codyswanngt/lisa-jira-claim
plugins/lisa/skills/lisa-jira-claim/SKILL.md
Idempotently claims one live Jira leaf ticket for direct Lisa work. Reuses jira-build-intake Phase 3b semantics through lisa-atlassian-access: configured ready-to-claimed transition, assign-only-if-unassigned, stable managed comment, and post-write verification.
$ install --global
skillsauthnpx skillsauth add codyswanngt/lisa lisa-jira-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:25 AM90.9s2 files scanned
SKILL.md
- name:
- lisa-jira-claim
- description:
- Idempotently claims one live Jira leaf ticket for direct Lisa work. Reuses jira-build-intake Phase 3b semantics through lisa-atlassian-access: configured ready-to-claimed transition, assign-only-if-unassigned, stable managed comment, and post-write verification.
- allowed-tools:
- ["Bash", "Skill", "Read"]
Claim Jira Ticket: $ARGUMENTS
Claim exactly one canonical Jira key. All Jira access goes through lisa-atlassian-access; do not call MCP tools or acli directly. This is the reusable direct-session counterpart of lisa-jira-build-intake Phase 3b.
-
Resolve merged
atlassian.cloudId,jira.project, andjira.workflowvalues from local-over-global config. Require the key's project prefix to equal the configured Jira project. Resolve ready, claimed, review, environment, and terminal roles from config; do not hardcode status decisions. -
Invoke
lisa-jira-read-ticket <key>immediately before mutation. Reject a resolved/terminal ticket, active blocker,repo:<other>ticket, any item with open children/subtasks, or an Epic perrepo-scope-splitandleaf-only-lifecycle. -
Inspect the live workflow role:
- Already claimed, review, environment-done, or another configured later non-terminal role -> preserve it and set
claim_outcome: reused. - Ready or an unlaned backlog leaf -> invoke
lisa-atlassian-access operation: transition key: <key> to: <configured-claimed>and require success. This is the idempotency lock. - Terminal/resolved -> reject; never regress completed work.
- Already claimed, review, environment-done, or another configured later non-terminal role -> preserve it and set
-
If and only if the ticket is unassigned, assign it to the authenticated account through
lisa-atlassian-access(prefer the identity-probed account id /@mesemantics documented by Jira build intake). Leave an existing assignee untouched. -
Post this stable comment once through
lisa-atlassian-access operation: comment, deduped against all existing comments:[lisa-tracker-claim] Claimed by Lisa. Starting implementation. -
Invoke
lisa-jira-read-ticket <key>again. Success requires an unresolved, current-repo leaf in claimed or a later non-terminal role. An unreachable transition or failed verification is a hard failure and must not authorize a binding. -
Return
tracker_provider: jira, canonicalwork_item_ref: <KEY>,claim_outcome: claimed|reused, assignee outcome, and the post-write status evidence.
Never create a ticket here. Never bypass lisa-atlassian-access.
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