CodySwannGT
CodySwannGT/lisa
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/CodySwannGT/lisa --skill lisa-jira-claimコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
This skill should be used for any non-trivial request — features, bugs, stories, epics, spikes, or multi-step tasks. It accepts a ticket URL (Jira, Linear, GitHub), a file path containing a spec, or a plain-text prompt. It assembles an agent team, breaks the work into structured tasks, and manages the full lifecycle from research through implementation, code review, deploy, and empirical verification.
any non-trivial request —…
This skill should be used for any non-trivial request — features, bugs, stories, epics, spikes, or multi-step tasks. It accepts a ticket URL (Jira, Linear, GitHub), a file path containing a spec, or a plain-text prompt. It assembles an agent team, breaks the work into structured tasks, and manages the full lifecycle from research through implementation, code review, deploy, and empirical verification.
SOC 職業分類に基づく
SKILL.md を表示中
| name | lisa-jira-claim |
| description | Idempotently claims one live… |
| allowed-tools | ["Bash","Skill","Read"] |
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, and jira.workflow values 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 per repo-scope-split and leaf-only-lifecycle.
Inspect the live workflow role:
claim_outcome: reused.lisa-atlassian-access operation: transition key: <key> to: <configured-claimed> and require success. This is the idempotency lock.If and only if the ticket is unassigned, assign it to the authenticated account through lisa-atlassian-access (prefer the identity-probed account id / @me semantics 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, canonical work_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.