plugins/lisa-copilot/skills/github-verify/SKILL.md
This skill should be used when verifying that a GitHub Issue meets organizational standards for parent-sub-issue relationships and description quality. It fetches the live issue and delegates the gate checks to github-validate-issue so the bar matches what github-write-issue enforces pre-write. The GitHub counterpart of lisa:jira-verify.
npx skillsauth add codyswanngt/lisa github-verifyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Verify that the existing GitHub Issue $ARGUMENTS (org/repo#<number> or full URL) meets organizational standards. This skill is a thin post-write wrapper around lisa:github-validate-issue: it fetches the live issue and asks the validator to run the gates against the fetched state.
This indirection exists so the gate definitions live in exactly one place (lisa:github-validate-issue). When the bar changes, change it there — lisa:github-verify, lisa:github-write-issue (Phase 5.5 pre-write), and lisa:github-to-tracker (PRD dry-run) all pick it up.
gh auth status succeeds.$ARGUMENTS. Resolve <org>, <repo>, <number>.gh issue view <number> --repo <org>/<repo> --json number,title,body,labels,state,milestone,assignees,author,createdAt,updatedAt,closed,closedAt,url.lisa:github-validate-issue and pass the issue ref. The validator fetches its own copy and runs every gate (Specification + Feasibility) against the live state.Pass through lisa:github-validate-issue's structured output unchanged. Do not summarize or paraphrase — downstream callers (e.g. lisa:github-agent's pre-flight gate) parse the gate lines.
## Validation Journey markdown section — same parser logic as lisa:github-add-journey and lisa:github-journey.tools
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
tools
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
tools
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
tools
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and