[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YTES898TRYQMSYNS7EXE4":3,"skill-same:01M72YTES898TRYQMSYNS7EXE4":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":28,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M72YTES898TRYQMSYNS7EXE4","implement-pr",null,"Sub-skill of agile-10-implement. Open (off base\u002Fmain) or update the PR for the ticket's pushed branch, linked to the Jira Story, with AC coverage + ADR-compliance sections. This skill — not implement-code — owns opening the PR. Posts the 🤖 pr marker. Not user-invoked.","cedricfarinazzo\u002Fagile-skills","cedricfarinazzo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34288081?v=4","01M72YSXQAMF9679DT1EGZV51E","01M72YSXRG377986J64G71PJZE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fagile-execution\u002Fskills\u002Fimplement-pr\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: implement-pr\ndescription: \"Sub-skill of agile-10-implement. Open (off base\u002Fmain) or update the PR for the ticket's pushed branch, linked to the Jira Story, with AC coverage + ADR-compliance sections. This skill — not implement-code — owns opening the PR. Posts the 🤖 pr marker. Not user-invoked.\"\nuser-invocable: false\n---\n\n# implement_pr\n\n## Host execution\n\n**Claude Code:** retain the agent-dispatch and concurrency behavior defined below. **Codex:** use only the inline behavior stated here.\n\nOn Codex this sub-skill runs inline under `agile-10-implement` with `concurrency=0`; never spawn or assume a named agent. Perform its full gate and return its normal receipt to the caller.\n\n## Purpose\n\nPR phase for `agile-10-implement`, invoked after `implement-code` pushed the branch. **This skill owns opening the PR**, off `\u003Cbase-branch>`. Idempotent — it updates an existing open PR rather than opening a duplicate.\n\n**Autonomous — never prompt the user.** This phase makes no product or design decisions: the build is done and it only describes it, so there is no critical-decision path here. Where the diff and the plan disagree, say so in the PR body and continue. This holds in `concurrency=0` inline mode too, where no agent wraps this skill.\n\n## Source the body from the real diff\n\nThe build is already done; this phase only describes it. Build the body from **the actual pushed diff** (`gh pr diff` \u002F `git diff \u003Cbase>...HEAD`) plus the ticket's `🤖 agile:phase=plan` and `🤖 agile:phase=implement` comments: the plan's AC→test map → **AC coverage** and **Testing**; the diff's files → **Changes**; the plan's flagged decisions and the `implement` comment's noted deviations → **ADR compliance**. Where the diff diverges from the plan, say so in the body — do not paper over it.\n\n## Open or update\n\n`gh pr list --state open --head \u003Cbranch> --json number,url` → found: `gh pr edit` (refresh title\u002Fbody); none: `gh pr create --base \u003Cbase-branch>`.\n\n**Staging the body through a file? Name it for the ticket** (`pr-\u003CTICKET>.md`, never `pr.md`) — concurrent phase agents share one temp dir, so a generic name lets a sibling's overwrite publish its ticket's body under yours. **Then verify what actually landed:** `gh pr view \u003CN> --json body` and confirm the ticket key is yours. `gh` reports success on the bytes it was handed, not on the ones you meant to write — a body naming another ticket is the one defect the author is structurally unable to notice.\n\n**Title:** `[TICKET] \u003CStory summary>`\n\n**Body sections:**\n- **Story** — link to the Jira ticket.\n- **What this PR does** — 2–3 sentences from the plan's intent.\n- **AC coverage** — each AC → the test that covers it, confirmed against the committed tests.\n- **Changes** — files\u002Fmodules touched and why, reconciled with the real diff; flag any addition or omission versus the plan.\n- **Testing** — unit \u002F integration \u002F manual, and the edge cases covered.\n- **Test tiers** — read the `agile:phase=implement` marker's `Mode` + gate receipt. Sequential: `Verified locally: lint + unit + integration + fresh-DB migration.` Concurrent: `Verified locally: lint + unit + typecheck (stack-free, worktree). Deferred to CI: integration + e2e + fresh-DB migration (concurrent build — CI is the gate).` This tells the merge train exactly which tiers CI must confirm.\n- **Specs UI match** — states implemented, plus any deviation and its reason (UI Stories).\n- **ADR compliance** — new decisions or libraries introduced, each flagged for the reviewer.\n- **Checklist** — ACs tested · lint\u002Ftype clean · no regressions · linked to Jira · Specs UI match · ADR compliance · test tiers stated.\n\n**Label a concurrent build** — when the `implement` marker's mode is `concurrent`, `gh pr edit \u003CN> --add-label integration-deferred` (create the label once if the repo lacks it). That label is the machine-readable signal `agile-11-merge-train` reads to know integration + e2e were not run locally. Sequential PRs carry no label.\n\nPost `🤖 agile:phase=pr` with the PR URL (noting the label on a concurrent build) and return the PR number.\n\nThis phase does **not** transition the Story — the orchestrator transitions to `In Review` only after `implement-review` approves, and never to `Done`.\n\n## Marker — mandatory, exact format\n\nPost via `mcp__atlassian__addCommentToJiraIssue` (`contentFormat=\"markdown\"`). The comment **must begin with the literal HTML comment** or resume detection (which greps `🤖 \u003C!-- agile:phase=... -->`) misses it and the phase re-runs. Never delete prior markers.\n\n```\n🤖 \u003C!-- agile:phase=pr --> **pr — agile-10-implement — \u003CYYYY-MM-DD>**\n\u003Cphase content>\n```\n","# implement_pr\n\n## Host execution\n\n**Claude Code:** retain the agent-dispatch and concurrency behavior defined below. **Codex:** use only the inline behavior stated here.\n\nOn Codex this sub-skill runs inline under `agile-10-implement` with `concurrency=0`; never spawn or assume a named agent. Perform its full gate and return its normal receipt to the caller.\n\n## Purpose\n\nPR phase for `agile-10-implement`, invoked after `implement-code` pushed the branch. **This skill owns opening the PR**, off `\u003Cbase-branch>`. Idempotent — it updates an existing open PR rather than opening a duplicate.\n\n**Autonomous — never prompt the user.** This phase makes no product or design decisions: the build is done and it only describes it, so there is no critical-decision path here. Where the diff and the plan disagree, say so in the PR body and continue. This holds in `concurrency=0` inline mode too, where no agent wraps this skill.\n\n## Source the body from the real diff\n\nThe build is already done; this phase only describes it. Build the body from **the actual pushed diff** (`gh pr diff` \u002F `git diff \u003Cbase>...HEAD`) plus the ticket's `🤖 agile:phase=plan` and `🤖 agile:phase=implement` comments: the plan's AC→test map → **AC coverage** and **Testing**; the diff's files → **Changes**; the plan's flagged decisions and the `implement` comment's noted deviations → **ADR compliance**. Where the diff diverges from the plan, say so in the body — do not paper over it.\n\n## Open or update\n\n`gh pr list --state open --head \u003Cbranch> --json number,url` → found: `gh pr edit` (refresh title\u002Fbody); none: `gh pr create --base \u003Cbase-branch>`.\n\n**Staging the body through a file? Name it for the ticket** (`pr-\u003CTICKET>.md`, never `pr.md`) — concurrent phase agents share one temp dir, so a generic name lets a sibling's overwrite publish its ticket's body under yours. **Then verify what actually landed:** `gh pr view \u003CN> --json body` and confirm the ticket key is yours. `gh` reports success on the bytes it was handed, not on the ones you meant to write — a body naming another ticket is the one defect the author is structurally unable to notice.\n\n**Title:** `[TICKET] \u003CStory summary>`\n\n**Body sections:**\n- **Story** — link to the Jira ticket.\n- **What this PR does** — 2–3 sentences from the plan's intent.\n- **AC coverage** — each AC → the test that covers it, confirmed against the committed tests.\n- **Changes** — files\u002Fmodules touched and why, reconciled with the real diff; flag any addition or omission versus the plan.\n- **Testing** — unit \u002F integration \u002F manual, and the edge cases covered.\n- **Test tiers** — read the `agile:phase=implement` marker's `Mode` + gate receipt. Sequential: `Verified locally: lint + unit + integration + fresh-DB migration.` Concurrent: `Verified locally: lint + unit + typecheck (stack-free, worktree). Deferred to CI: integration + e2e + fresh-DB migration (concurrent build — CI is the gate).` This tells the merge train exactly which tiers CI must confirm.\n- **Specs UI match** — states implemented, plus any deviation and its reason (UI Stories).\n- **ADR compliance** — new decisions or libraries introduced, each flagged for the reviewer.\n- **Checklist** — ACs tested · lint\u002Ftype clean · no regressions · linked to Jira · Specs UI match · ADR compliance · test tiers stated.\n\n**Label a concurrent build** — when the `implement` marker's mode is `concurrent`, `gh pr edit \u003CN> --add-label integration-deferred` (create the label once if the repo lacks it). That label is the machine-readable signal `agile-11-merge-train` reads to know integration + e2e were not run locally. Sequential PRs carry no label.\n\nPost `🤖 agile:phase=pr` with the PR URL (noting the label on a concurrent build) and return the PR number.\n\nThis phase does **not** transition the Story — the orchestrator transitions to `In Review` only after `implement-review` approves, and never to `Done`.\n\n## Marker — mandatory, exact format\n\nPost via `mcp__atlassian__addCommentToJiraIssue` (`contentFormat=\"markdown\"`). The comment **must begin with the literal HTML comment** or resume detection (which greps `🤖 \u003C!-- agile:phase=... -->`) misses it and the phase re-runs. Never delete prior markers.\n\n```\n🤖 \u003C!-- agile:phase=pr --> **pr — agile-10-implement — \u003CYYYY-MM-DD>**\n\u003Cphase content>\n```\n",{"name":5,"description":7,"user-invocable":19},"master","5f163e1c0720bcc8f5c9caf4e675c301585b3b29","agile-execution\u002Fskills\u002Fimplement-pr","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo","https:\u002F\u002Fcedricfarinazzo.fr\u002F","IT engineer specialized in Cybersecurity and SRE\u002FDevOps","2026-11-13 03:28:11",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add cedricfarinazzo\u002Fagile-skills --skill implement-pr",{"tool":37,"command":38},"bunx","bunx skills add cedricfarinazzo\u002Fagile-skills --skill implement-pr",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cedricfarinazzo\u002Fagile-skills --skill implement-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fagile-execution\u002Fskills\u002Fimplement-pr\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M72YXMSVD28QYHJ70AVJ9SBP","session-audit","Audit the cost and efficiency of Claude Code sessions that ran agile-skills: per-skill and per-subagent spend, a before\u002Fafter delta normalised by work shipped, and ranked skill improvements. Triggers: audit this session's cost, analyze the session transcripts, compare before and after sessions, is the new version more efficient, where do the tokens go, subagent cost breakdown, find efficiency improvements.","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fsession-audit\u002Fskills\u002Fsession-audit\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M72YXG2E8CAD3YHTHFESKF2B","deep-it-project-review","Autonomously perform a deep, evidence-backed technical review of a software or IT project across applicable architecture, code, security, delivery, operations, and lifecycle domains without modifying project files. Triggers: deep IT project review, technical project review, architecture audit, repository assessment, assess this codebase, review this project.","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fproject-review\u002Fskills\u002Fdeep-it-project-review\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M72YXBQJCSDC60PVKA6H9SJ3","test-refactor","Audit one test suite at a time for dead weight, duplication, parallel-unsafety and runtime cost, or characterize behavior before a risky refactor — with production code frozen and good coverage kept, proven per module rather than assumed. Triggers: test refactor, characterize before refactor, characterization tests, clean the tests, refactor the tests, test suite audit, DRY the tests, parallelize the test suite, speed up the tests.","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fdeep-refactor\u002Fskills\u002Ftest-refactor\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M72YX7QCP7MA1H2DSWVG6Y4C","doc-refactor","Audit every markdown file in a repo — READMEs, docs\u002F, and agent-instruction files — for lies, drift, duplication and bloat, then ticket and ship the cleanup as a sequenced PR train, with source code frozen and every surviving claim verified against the repo rather than read. Triggers: doc refactor, refactor the docs, clean the docs, documentation audit, README audit, docs are stale, DRY the docs, audit every markdown file.","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fdeep-refactor\u002Fskills\u002Fdoc-refactor\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M72YX36Z9MSECJH7FJ4JM09Z","deep-refactor","Audit an entire codebase for defects, waste and debt, then ticket and ship the findings as a sequenced PR train — without breaking the test contract. Triggers: deep refactor, refactor audit, clean the codebase, DRY pass, audit and fix everything.","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fdeep-refactor\u002Fskills\u002Fdeep-refactor\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M72YWZ1HEXSKQ7JCSVR2HPT0","agile-sprint-drain","Drain the active sprint to a fixed point: auto-alternate agile-10-implement (build) and agile-11-merge-train (merge) until both empty (DRAINED) or blocked (STUCK). Optional concurrency=N, dispatch=session, max-merges=N. Triggers: drain the sprint, run the sprint to completion, implement and merge until done, clear the whole board, ship the sprint.","https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fagile-sprint-drain\u002Fskills\u002Fagile-sprint-drain\u002FSKILL.md",[],[]]