[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YTWG37HT9WPP5QGS9N49P":3,"skill-same:01M72YTWG37HT9WPP5QGS9N49P":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},"01M72YTWG37HT9WPP5QGS9N49P","merge-fix-until-satisfied",null,"Fix every PR review issue, commit, push, re-check until satisfied. Triggers: fix all, fix everything, \u002Ffix-until-satisfied. After merge-review-pr.","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-merge-review\u002Fskills\u002Fmerge-fix-until-satisfied\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: merge-fix-until-satisfied\ndescription: \"Fix every PR review issue, commit, push, re-check until satisfied. Triggers: fix all, fix everything, \u002Ffix-until-satisfied. After merge-review-pr.\"\n---\n\n# merge-fix-until-satisfied\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-11-merge-train` 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\nFix every issue from a PR review, commit, re-examine, repeat until satisfied. The `\"Satisfied. No remaining issues.\"` verdict is the contract callers (`agile-11-merge-train` 3c) gate on.\n\n**Input:** the issues from the current session (`merge-review-pr` output or an inline review). No review yet → run `merge-review-pr` first.\n\n**Verification mode (0 issues) is valid usage, not a smell.** When the caller passes \"0 issues\", still run and still emit the verdict — never refuse with \"nothing to do\". Phase 1 becomes *opportunistic cleanup*: while re-reading the changed files, fix anything genuinely ugly you find.\n\n**Cleanup threshold — obvious and low-risk only.** In scope: an unused import, a dead branch, a misleading name, copy-paste worth extracting (≥3 lines), a comment the code contradicts, a magic number that wants a named constant, an f-string SQL that wants bound params. Out of scope (file a follow-up ticket instead): a restructured class hierarchy, a new abstraction layer, splitting a module, renaming a public API, or touching any file the PR did not already modify. Unsure whether it is an improvement → leave it. The cleanup belongs in the PR being merged, not sprawled into adjacent code.\n\n## Phase 1 — Fix\n\nNo review issues and nothing ugly spotted → skip to Phase 3. Otherwise, per issue (critical first, then minor):\n\n1. **Read the full file before editing** — never edit from diff context alone.\n2. Apply the fix.\n3. **Grep for analogous sites.** Fixing a field name means grepping every test file for the old name; a wrong port in one docstring means checking its siblings. One fix, then the sweep.\n4. Run the project's linter on the file (`ruff check`, `eslint`, `golangci-lint`, …). Markdown \u002F YAML \u002F TOML \u002F JSON have no linter — just verify the file still parses.\n\n**Under a round budget (`round=` from the caller, e.g. `agile-11-merge-train`):** this is the only fix push before a final delta review. Fix only the findings named, with the smallest change that resolves each. No opportunistic cleanup, in verification mode too, and no analogous-site sweep beyond files the fix touches; every extra edit is new surface for that review.\n\n**\"Fix all\" means fix all, including every Minor.** Minor is a severity, not permission to punt. The only acceptable skip is genuinely separate work in files the PR did not already touch, never one that is merely more effort — file a follow-up inline and note it in the postmortem. Never declare Satisfied with unaddressed Minor findings on the report.\n\nIf a fix reveals a deeper problem, escalate and explain before proceeding.\n\n## Phase 2 — Commit & push\n\nNo-op Phase 1 → skip to Phase 3. Otherwise group related fixes into one commit and separate unrelated ones. **Keep opportunistic cleanup separate from review-issue fixes**: `refactor(scope):` \u002F `style(scope):` for cleanup, `fix(scope):` for review corrections.\n\n```\nfix(\u003Cscope>): \u003Cticket> \u003Cimperative summary>\n\n\u003Cbody only if the why is non-obvious>\n```\n\n**Lint before the push.** Run every command the CI lint job runs on the tree you are about to push, not only Phase 1's per-file linter, and read each real exit code. Fix and re-run until each exits 0; a lint failure CI finds costs the caller a whole 3e round.\n\nThen `git push origin \u003Cbranch>` where `\u003Cbranch>` is whatever HEAD is on (`git rev-parse --abbrev-ref HEAD`) — a PR feature branch, or `main` itself when a person runs this on a post-merge follow-up outside the autonomous loop. Inside the loop work lands only through a PR, and the agile-mods push guard refuses a push to `main`.\n\n**Confirm you are on the right branch BEFORE committing.** Your caller resolves one working location per PR and names it in your prompt — often a worktree that already holds the branch, because `agile-10-implement` leaves one per unmerged ticket. Work there by absolute path (`cd \u003Cpath>`, `git -C \u003Cpath>`) and check `git -C \u003Cpath> rev-parse --abbrev-ref HEAD` matches the PR's branch. If it does not — most dangerously if it says `main` while you were asked to fix a PR — **stop and emit the receipt with `blocked`**; do not commit. \"Whatever HEAD is on\" is the push rule, not a licence to commit a PR's fixes wherever the shell happens to be pointing.\n\n## Phase 3 — Re-examine\n\nRe-read **every** file changed, in the original PR and in the fixes. Did a fix introduce something new (did every reference update)? Are there analogous issues in untouched files? Does the test-suite `CLAUDE.md\u002FAGENTS.md` need updating?\n\n## Phase 4 — Verdict\n\n**Satisfaction is a multi-gate check, not a vibe.** Emit `\"Satisfied. No remaining issues.\"` only when every gate below is provably green; any failure loops back to Phase 1.\n\n**Do not poll or wait for CI.** Capture the latest run id **before** pushing (`gh run list --branch \u003Cbranch> -L1 --json databaseId`), push, then emit the receipt immediately naming that pre-push run id and the pushed sha. Waiting for the post-push run is the **caller's** gate (`agile-11-merge-train` 3e); a poll loop here burns the whole step's budget and returns nothing.\n\n1. **CI accounted for** — read the checks on branch HEAD **once** (`gh pr view \u003CN> --json statusCheckRollup,mergeStateStatus`). A non-SUCCESS conclusion on a **pre-existing** run must be diagnosed and fixed here. An in-progress or not-yet-started run on the tip *you just pushed* is not a gate failure — record the pre-push id + pushed sha and hand off. One read, no loop.\n2. **Lint clean** — the project linter exits 0 across all touched paths.\n3. **All ACs satisfied** — walk the Jira ticket's AC list one by one; if you cannot point at a specific line, it is not satisfied.\n4. **PR up to date with main** — `gh pr view \u003CN> --json mergeable,mergeStateStatus` returns `mergeable: MERGEABLE` + `mergeStateStatus: CLEAN`. `BEHIND` \u002F `DIRTY` \u002F `CONFLICTING` → invoke `merge-update-pr` before declaring satisfaction.\n5. **Implementation quality** — re-read the changed files (diff context is not enough): clean, DRY, no dead branches, no duplication worth extracting, no misleading names, no contradicted comments, no unused imports, no unnamed magic numbers. Anything surfacing here goes back through Phase 1.\n\n**A DoD-vs-convention conflict is a labelled conscious accept, never a silent choice in either direction.** When a standing repo convention contradicts the ticket's DoD wording, follow the convention and record a `Conscious accept:` entry stating all five: what the DoD asks · what was done instead · why the convention wins · **where the equivalent-strength coverage actually lives** · that this was deliberate. It carries into the postmortem so the merge\u002FQA reader signs off knowingly; unlabelled it reads later as a missed DoD item. `none` is a real value of that field, not an omission.\n\n```\nSatisfied. No remaining issues.\n- CI: pre-push run \u003Crun-id>, pushed sha \u003Csha> — caller gates the fresh run\n- Lint: clean\n- ACs: \u003CN>\u002F\u003CN> verified against specific lines\n- Conscious accept: \u003CDoD asks X> → \u003Cdid Y per convention Z>; equivalent coverage at \u003Cfile:line>; deliberate   |   none\n- Rebase: branch up to date with main, no conflicts\n- Implementation: \u003Cone-line quality assessment>\n```\n\nNot satisfied → name which gate(s) failed and what blocks them, then loop back to Phase 1.\n\n**Never end the turn without the verdict receipt, and never ask the caller a question** — blocked means emitting the receipt with a `blocked` field naming the blocker. The receipt is structured fields, written in normal English full sentences: the merge train reads it as the green light for merge, and it must stay unambiguous when read later.\n","# merge-fix-until-satisfied\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-11-merge-train` 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\nFix every issue from a PR review, commit, re-examine, repeat until satisfied. The `\"Satisfied. No remaining issues.\"` verdict is the contract callers (`agile-11-merge-train` 3c) gate on.\n\n**Input:** the issues from the current session (`merge-review-pr` output or an inline review). No review yet → run `merge-review-pr` first.\n\n**Verification mode (0 issues) is valid usage, not a smell.** When the caller passes \"0 issues\", still run and still emit the verdict — never refuse with \"nothing to do\". Phase 1 becomes *opportunistic cleanup*: while re-reading the changed files, fix anything genuinely ugly you find.\n\n**Cleanup threshold — obvious and low-risk only.** In scope: an unused import, a dead branch, a misleading name, copy-paste worth extracting (≥3 lines), a comment the code contradicts, a magic number that wants a named constant, an f-string SQL that wants bound params. Out of scope (file a follow-up ticket instead): a restructured class hierarchy, a new abstraction layer, splitting a module, renaming a public API, or touching any file the PR did not already modify. Unsure whether it is an improvement → leave it. The cleanup belongs in the PR being merged, not sprawled into adjacent code.\n\n## Phase 1 — Fix\n\nNo review issues and nothing ugly spotted → skip to Phase 3. Otherwise, per issue (critical first, then minor):\n\n1. **Read the full file before editing** — never edit from diff context alone.\n2. Apply the fix.\n3. **Grep for analogous sites.** Fixing a field name means grepping every test file for the old name; a wrong port in one docstring means checking its siblings. One fix, then the sweep.\n4. Run the project's linter on the file (`ruff check`, `eslint`, `golangci-lint`, …). Markdown \u002F YAML \u002F TOML \u002F JSON have no linter — just verify the file still parses.\n\n**Under a round budget (`round=` from the caller, e.g. `agile-11-merge-train`):** this is the only fix push before a final delta review. Fix only the findings named, with the smallest change that resolves each. No opportunistic cleanup, in verification mode too, and no analogous-site sweep beyond files the fix touches; every extra edit is new surface for that review.\n\n**\"Fix all\" means fix all, including every Minor.** Minor is a severity, not permission to punt. The only acceptable skip is genuinely separate work in files the PR did not already touch, never one that is merely more effort — file a follow-up inline and note it in the postmortem. Never declare Satisfied with unaddressed Minor findings on the report.\n\nIf a fix reveals a deeper problem, escalate and explain before proceeding.\n\n## Phase 2 — Commit & push\n\nNo-op Phase 1 → skip to Phase 3. Otherwise group related fixes into one commit and separate unrelated ones. **Keep opportunistic cleanup separate from review-issue fixes**: `refactor(scope):` \u002F `style(scope):` for cleanup, `fix(scope):` for review corrections.\n\n```\nfix(\u003Cscope>): \u003Cticket> \u003Cimperative summary>\n\n\u003Cbody only if the why is non-obvious>\n```\n\n**Lint before the push.** Run every command the CI lint job runs on the tree you are about to push, not only Phase 1's per-file linter, and read each real exit code. Fix and re-run until each exits 0; a lint failure CI finds costs the caller a whole 3e round.\n\nThen `git push origin \u003Cbranch>` where `\u003Cbranch>` is whatever HEAD is on (`git rev-parse --abbrev-ref HEAD`) — a PR feature branch, or `main` itself when a person runs this on a post-merge follow-up outside the autonomous loop. Inside the loop work lands only through a PR, and the agile-mods push guard refuses a push to `main`.\n\n**Confirm you are on the right branch BEFORE committing.** Your caller resolves one working location per PR and names it in your prompt — often a worktree that already holds the branch, because `agile-10-implement` leaves one per unmerged ticket. Work there by absolute path (`cd \u003Cpath>`, `git -C \u003Cpath>`) and check `git -C \u003Cpath> rev-parse --abbrev-ref HEAD` matches the PR's branch. If it does not — most dangerously if it says `main` while you were asked to fix a PR — **stop and emit the receipt with `blocked`**; do not commit. \"Whatever HEAD is on\" is the push rule, not a licence to commit a PR's fixes wherever the shell happens to be pointing.\n\n## Phase 3 — Re-examine\n\nRe-read **every** file changed, in the original PR and in the fixes. Did a fix introduce something new (did every reference update)? Are there analogous issues in untouched files? Does the test-suite `CLAUDE.md\u002FAGENTS.md` need updating?\n\n## Phase 4 — Verdict\n\n**Satisfaction is a multi-gate check, not a vibe.** Emit `\"Satisfied. No remaining issues.\"` only when every gate below is provably green; any failure loops back to Phase 1.\n\n**Do not poll or wait for CI.** Capture the latest run id **before** pushing (`gh run list --branch \u003Cbranch> -L1 --json databaseId`), push, then emit the receipt immediately naming that pre-push run id and the pushed sha. Waiting for the post-push run is the **caller's** gate (`agile-11-merge-train` 3e); a poll loop here burns the whole step's budget and returns nothing.\n\n1. **CI accounted for** — read the checks on branch HEAD **once** (`gh pr view \u003CN> --json statusCheckRollup,mergeStateStatus`). A non-SUCCESS conclusion on a **pre-existing** run must be diagnosed and fixed here. An in-progress or not-yet-started run on the tip *you just pushed* is not a gate failure — record the pre-push id + pushed sha and hand off. One read, no loop.\n2. **Lint clean** — the project linter exits 0 across all touched paths.\n3. **All ACs satisfied** — walk the Jira ticket's AC list one by one; if you cannot point at a specific line, it is not satisfied.\n4. **PR up to date with main** — `gh pr view \u003CN> --json mergeable,mergeStateStatus` returns `mergeable: MERGEABLE` + `mergeStateStatus: CLEAN`. `BEHIND` \u002F `DIRTY` \u002F `CONFLICTING` → invoke `merge-update-pr` before declaring satisfaction.\n5. **Implementation quality** — re-read the changed files (diff context is not enough): clean, DRY, no dead branches, no duplication worth extracting, no misleading names, no contradicted comments, no unused imports, no unnamed magic numbers. Anything surfacing here goes back through Phase 1.\n\n**A DoD-vs-convention conflict is a labelled conscious accept, never a silent choice in either direction.** When a standing repo convention contradicts the ticket's DoD wording, follow the convention and record a `Conscious accept:` entry stating all five: what the DoD asks · what was done instead · why the convention wins · **where the equivalent-strength coverage actually lives** · that this was deliberate. It carries into the postmortem so the merge\u002FQA reader signs off knowingly; unlabelled it reads later as a missed DoD item. `none` is a real value of that field, not an omission.\n\n```\nSatisfied. No remaining issues.\n- CI: pre-push run \u003Crun-id>, pushed sha \u003Csha> — caller gates the fresh run\n- Lint: clean\n- ACs: \u003CN>\u002F\u003CN> verified against specific lines\n- Conscious accept: \u003CDoD asks X> → \u003Cdid Y per convention Z>; equivalent coverage at \u003Cfile:line>; deliberate   |   none\n- Rebase: branch up to date with main, no conflicts\n- Implementation: \u003Cone-line quality assessment>\n```\n\nNot satisfied → name which gate(s) failed and what blocks them, then loop back to Phase 1.\n\n**Never end the turn without the verdict receipt, and never ask the caller a question** — blocked means emitting the receipt with a `blocked` field naming the blocker. The receipt is structured fields, written in normal English full sentences: the merge train reads it as the green light for merge, and it must stay unambiguous when read later.\n",{"name":5,"description":7},"master","5f163e1c0720bcc8f5c9caf4e675c301585b3b29","agile-merge-review\u002Fskills\u002Fmerge-fix-until-satisfied","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 merge-fix-until-satisfied",{"tool":37,"command":38},"bunx","bunx skills add cedricfarinazzo\u002Fagile-skills --skill merge-fix-until-satisfied",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cedricfarinazzo\u002Fagile-skills --skill merge-fix-until-satisfied","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcedricfarinazzo\u002Fagile-skills\u002Fblob\u002Fmaster\u002Fagile-merge-review\u002Fskills\u002Fmerge-fix-until-satisfied\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",[],[]]