codyswanngt/github-verify
plugins/lisa-agy/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.
$ install --global
skillsauthnpx skillsauth add codyswanngt/lisa github-verifyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 1, 2026, 4:27 AM325.9s1 file scanned
SKILL.md
- name:
- github-verify
- description:
- 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.
- allowed-tools:
- ["Skill", "Bash"]
Verify GitHub Issue: $ARGUMENTS
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.
Process
- Confirm
gh auth statussucceeds. - Parse
$ARGUMENTS. Resolve<org>,<repo>,<number>. - Fetch the issue via
gh issue view <number> --repo <org>/<repo> --json number,title,body,labels,state,milestone,assignees,author,createdAt,updatedAt,closed,closedAt,url. - Invoke
lisa:github-validate-issueand pass the issue ref. The validator fetches its own copy and runs every gate (Specification + Feasibility) against the live state. - Surface the validator's report verbatim to the caller.
Output
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.
Notes
- This skill is read-only. It never edits the issue, posts comments, or changes labels.
- If a gate fails, the recommendation is part of the validator's report; surface it as-is.
- The Validation Journey check (S11) parses the
## Validation Journeymarkdown section — same parser logic aslisa:github-add-journeyandlisa:github-journey.
Related Skills
codyswanngt/lisa-setup-workstation
development
VerifiedTrustedCommunity
Prepare a machine — a fresh laptop or a throwaway container — to run coding agents, before any repository exists. Detects which of Lisa's supported agents (Claude Code, Codex, Cursor, OpenCode, Antigravity, Copilot) are already installed, asks which credential manager the machine uses (Bitwarden, 1Password, Doppler, Vault, AWS, or none), and installs only what is missing, each by its vendor's own preferred method. Idempotent, headless by default, and emits a Dockerfile for a spin-up/spin-down environment. Run it on a new machine, in a container, or before cloning anything.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-setup-remote-env
tools
VerifiedTrustedCommunity
Provision and verify a remote execution environment for a host project — Codex Cloud today, other remote surfaces as they are added. Generates a repository-owned setup script that installs the declared toolchain, materializes secrets through lisa-secrets-access, and runs the project's own hook. Provisions by API where one exists, by driving the vendor console where one does not, and by emitting exact config otherwise — then proves the result with the same read-back regardless of which tier did the work. Use before dispatching any work with executionEnv.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-setup-local-env
tools
VerifiedTrustedCommunity
Bring a developer's machine in line with the toolchain the project declares. Reports every tool in remoteEnv.tools that is missing, outdated, or unpinned for this platform, and installs the missing ones into ~/.local/bin from the same pinned, checksummed entries the remote surfaces use — but only when asked. Same manifest, same pins, same installers as lisa-setup-remote-env; what differs is consent and that the pin is a floor rather than an equality. Run it on a fresh checkout, after a manifest change, or when a tool fails at the moment of use.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-remote-dispatch
tools
VerifiedTrustedCommunity
Route one unit of work to a remote execution surface. Reads the executionEnv parameter (local by default, codex-cloud or claude-web today), verifies the environment is provisioned and bound to this repository, submits a thin skill invocation, records the task identifier to .lisa/remote-dispatch.json, and exits without polling. Routing only — the remote runs the identical skill from the identical repository. Composable and inline: other skills invoke it via the Skill tool rather than users calling it directly.
3SKILL.mdUpdated Aug 30, 2026