plugins/lisa/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.documentation
Onboard a user to the project via its LLM Wiki. Interviews the user about themselves in relation to the project, captures that to project-scoped memory only, then gives a guided tour of what the project is and sample questions they can ask. Use when someone is new to the project or asks to be onboarded. Read-mostly — it does not open PRs or write PII into the wiki.
documentation
Migrate an existing, hand-rolled wiki implementation onto the lisa-wiki kernel — phased and compatibility-first, with a strict no-loss guarantee. Use when adopting lisa-wiki in a repo that already has its own wiki/, ingest skills, docs, or roles. Renaming things into the canonical shape is fine; losing functionality or data is not. Ends by running /doctor.
development
Health-check the LLM Wiki. Reports orphan pages, contradictions, stale claims, broken internal links, missing index/log coverage, structure-manifest violations, and secret/tenant leaks. Use periodically or before hardening a wiki. Read-only — it reports findings, it does not fix them.
testing
Ingest source material into the LLM Wiki. With an argument (URL, file path, or prompt) it ingests that one source; with no argument it runs a full ingest across every enabled non-external-write source. Routes to the right connector, then runs the ordered pipeline (source note → synthesis → index → log → verify → state → commit/PR). Use whenever new knowledge should enter the wiki.