codyswanngt/lisa-github-claim
plugins/lisa-cursor/skills/lisa-github-claim/SKILL.md
Idempotently claims one live GitHub leaf issue for direct Lisa work. Reuses github-build-intake Phase 3b semantics: configured ready-to-claimed relabel, assign-only-if-unassigned, stable managed comment, and post-write verification.
$ install --global
skillsauthnpx skillsauth add codyswanngt/lisa lisa-github-claimInstall 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: Jul 20, 2026, 3:10 AM17.5s1 file scanned
SKILL.md
- name:
- lisa-github-claim
- description:
- Idempotently claims one live GitHub leaf issue for direct Lisa work. Reuses github-build-intake Phase 3b semantics: configured ready-to-claimed relabel, assign-only-if-unassigned, stable managed comment, and post-write verification.
- allowed-tools:
- ["Bash", "Skill", "Read"]
Claim GitHub Issue: $ARGUMENTS
Claim exactly one canonical org/repo#<number> reference. This is the reusable direct-session counterpart of lisa-github-build-intake Phase 3b.
-
Resolve merged
.github.org,.github.repo, optional.github.queueRepo, andgithub.labels.buildvalues from local-over-global config. Resolve current-repository identity independently usingrepo-scope-split/config-resolution(.repo->.github.repo->git remote get-url originbasename). The queue repository defaults to<github.org>/<github.repo>; it is only the tracker storage/scan target and never replaces current-repository identity. Resolve the ready and claimed roles from config (defaultsstatus:readyandstatus:in-progress); do not hardcode lifecycle decisions. -
Require the ref's
org/repoto equal the resolved queue repository. Invokelisa-github-read-issue <ref>immediately before mutation. When the queue repository differs from the current repository, require exactly the current-repository scope (repo:<current>); reject an unlabeled issue,repo:<other>, or an ambiguous multi-repo leaf. Also reject a closed issue, an active blocker, any issue with open child work, or a childless Epic perrepo-scope-splitandleaf-only-lifecycle. -
Inspect the live build lifecycle labels:
- Already claimed, review, environment-done, or another configured later non-terminal role -> preserve it and set
claim_outcome: reused. - Ready or no build lifecycle label -> run
gh issue edit <number> --repo <org>/<repo>, remove ready when present, and add claimed. This is the idempotency lock. - Terminal label/state -> reject; completed work cannot be rebound as new work.
- Already claimed, review, environment-done, or another configured later non-terminal role -> preserve it and set
-
If and only if the issue is unassigned, add
@me; leave every existing assignee untouched. -
Post the stable marker comment once, deduped against all existing comments:
[lisa-tracker-claim] Claimed by Lisa. Starting implementation. -
Invoke
lisa-github-read-issue <ref>again. Success requires the issue to remain open, leaf/current-repo (including the explicitrepo:<current>proof for an umbrella queue), and in claimed or a later non-terminal role. If the relabel or verification fails, return failure and do not authorize a binding. -
Return
tracker_provider: github, canonicalwork_item_ref: <org>/<repo>#<number>,claim_outcome: claimed|reused, assignee outcome, and the post-write status evidence.
Never create an issue here. Never call GitHub for a configured Jira or Linear project.
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