[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0CJ09TSN5H7H6QWHVYFJG":3,"skill-same:01M7F0CJ09TSN5H7H6QWHVYFJG":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F0CJ09TSN5H7H6QWHVYFJG","ship-issue",null,"Address a GitHub issue in a dedicated git worktree -- implement, gate, obtain exact-HEAD reviews, open a PR, and hand protected merge ownership to the parent. Use when the user names an issue URL or number and wants it shipped.","nredd\u002Fpi-harness","nredd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13305966?v=4","01M7F0BM37W1RA8H414NPR8DA2","Nicholas Redd","01M7F0BM3WAMMSDBJPB1AM308V",2,"MIT","https:\u002F\u002Fgithub.com\u002Fnredd\u002Fpi-harness\u002Fblob\u002Fmain\u002Fpackages\u002Fpreset\u002Fskills\u002Fship-issue\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: ship-issue\ndescription: Address a GitHub issue in a dedicated git worktree -- implement, gate, obtain exact-HEAD reviews, open a PR, and hand protected merge ownership to the parent. Use when the user names an issue URL or number and wants it shipped.\nargument-hint: \u003Cissue-url-or-number> [extra instructions]\n---\n\n# ship-issue\n\nTake a GitHub issue from \"here is the URL\" to a reviewed PR in an isolated worktree. The parent\nowns the final critic, native CI monitoring, and protected merge outcome; a delegated\nworker hands those back with concrete handles.\n\nThe repo's own `CLAUDE.md` \u002F `AGENTS.md` OVERRIDES everything below. Read it first (step 3) and\nlet it win on gate commands, coverage bars, layout, and style. This file is the procedure, not\nthe house rules.\n\nAnything you emit -- commit messages, PR bodies, review comments, the final report -- follows\nthe user's configured writing style (their global agent instructions, when they have any). The\ndefault style, absent other instructions: bare colon-terminated lead-ins plus `-` bullets, NO\nmarkdown headers, no checkbox lists, `--` never em-dashes, backtick every identifier and path.\nThe headers in *this* file are instructions to you, not a template.\n\n## 1. Resolve the issue\n\nAccept a full URL, `#128`, or a bare `128`. From a URL, pull owner\u002Frepo too -- it may not be the\ncwd repo.\n\n- `gh issue view \u003CN> --json number,title,body,labels,state,comments`\n- Read the comments, not just the body. Prior design context and scope cuts usually live there\n- STOP and report if: the issue is closed, or `gh pr list --search \"\u003CN>\"` shows an open PR\n  already addressing it. Do not double-ship\n- If two readings of the issue produce materially different work, ask before implementing. If\n  it is merely underspecified, make the call a careful colleague would make and say which\n  assumption you took\n\n## 2. Worktree\n\nNever work in the user's checkout. One issue, one worktree.\n\n- `git -C \u003Crepo> fetch origin` then `git -C \u003Crepo> worktree prune` (stale `prunable` entries\n  accumulate)\n- Branch: `\u003Cprefix>\u002Fissue-\u003CN>`. `\u003Cprefix>` is the repo's documented branch-prefix convention\n  (check `AGENTS.md` \u002F `CONTRIBUTING.md` and recent branches), else the operator's GitHub login\n  (`gh api user --jq .login`). Append a short kebab slug from the title when the bare number is\n  ambiguous or the repo has several open issues in the same area -- e.g.\n  `\u003Cprefix>\u002Fissue-103-flaky-port-race`\n- Path: a SIBLING of the repo root, `\u003Cparent-of-repo>\u002Fissue-\u003CN>`. For\n  `\u002Fwork\u002Fplugins\u002Fexample-repo` that is `\u002Fwork\u002Fplugins\u002Fissue-\u003CN>`\n- `git -C \u003Crepo> worktree add -b \u003Cbranch> \u003Cpath> origin\u002F\u003Cdefault-branch>`\n- Do NOT use the `EnterWorktree` tool. It does not honor this layout\n- Every subsequent command runs with `\u003Cpath>` as cwd. Pass it explicitly (`git -C`, `make -C`,\n  absolute paths) rather than relying on shell state\n\n## 3. Read the repo's rules\n\n- Root `CLAUDE.md` \u002F `AGENTS.md`, plus any directory-scoped ones near the files you will touch\n- `Makefile` targets -- that is where the real gate is defined\n- `CONTRIBUTING.md`, `CHANGELOG.md` (does the repo keep one? Keep a Changelog format?)\n\nNote the hard rules explicitly before writing code. They are the ones the reviewers will check\nagainst, and the ones that make a PR bounce. Typical shapes: no inline waivers (`noqa`,\n`type: ignore`), a coverage floor, modules that must stay import-light, version strings that\nlive in more than one file, a required changelog entry.\n\n## 4. Implement\n\nOrdinary work, scoped to the issue. Tests by default -- the repo's existing test layout tells\nyou where they go and what style they are in.\n\n- Match the surrounding code's idiom, naming, comment density, and docstring form\n- Update the changelog if the repo keeps one\n- Update docs if the change is user-facing and the repo has a docs tree\n- Do not widen scope. If you find an adjacent bug, note it for the report; fix it only if the\n  change is unshippable without it, and say so in the PR body\n\n## 5. Gate -- before review, not after\n\nRun the repo's real gate and capture the ACTUAL output. It becomes the `Verification:` bullets.\n\n- `make all` when the `Makefile` defines it. Otherwise the closest equivalent: format, lint,\n  type check, tests\n- `uv run prek run --all-files` (or `pre-commit run --all-files`) when the repo has a\n  `.pre-commit-config.yaml`. Local hooks gate commits; a manual run catches what you would\n  otherwise discover at push time\n- Lockfile check and build if the repo has them (`uv lock --check`, `uv build`)\n\nRed gate means do not proceed. Fix it, or stop and report why it cannot be made green. Never\nship on a gate you did not actually run -- \"the imports resolved\" is not evidence.\n\n## 6. Commit and push\n\n- Subject: capitalized imperative, no trailing period, no conventional-commit prefix (no\n  `feat:` \u002F `fix:` \u002F `chore:`)\n- Body only when the subject cannot carry it. Then `Changes:` plus `-` bullets, one concrete\n  change each, phrased \"Verb the `thing`\"\n- Keep the `Co-Authored-By: Claude ...` footer. Attribution is a footer, not a writing style --\n  the body above it reads like the user\n- `git push -u origin \u003Cbranch>`\n- Never `git push --force` to the default branch. Force-push only your own issue branch, and\n  only with `--force-with-lease`\n\n## 7. Review round -- exact final HEAD\n\nAfter the gate, use `\u002Fskill:code-review` for the separate Standards and Spec axes. Run one dedicated\n`critic` only when your actual allowed-subagent list permits it. A delegated worker restricted to\n`code-reviewer` opens the PR and returns the original axis reports and concrete handles with\n`Parent critic: PENDING`. Keep permissions unchanged. The parent must run its independent\nfinal-HEAD critic BEFORE merge admission, even if a permitted worker ran one.\n\nWhoever runs a critic spawns `Agent(subagent_type: \"critic\")` with no `model`; its `agentModels`\ntier picks the model. Only when the issue is design-level (new module or public interface,\nconcurrency, persistence or wire format, auth), add a second\n`Agent(subagent_type: \"critic\", model: \"@frontier\")`. Name tiers, never model ids. If either route\nis quota-parked, wait; do not silently substitute a model or another tier.\n\nThe shared skill selects parent background versus delegated blocking calls, supplies both full SHAs\nand the original whole-PR range, and renews it after a HEAD change. Pass the issue\u002Fspec and repo\nrules; do not use the ambiguous `\u002Fcode-review` workflow command.\n\nThe critic is supplementary, never a substitute for either axis. It is read-only and already\ncarries the refute-before-report rule, so name the final diff and issue only. Its receipt preserves\nthe original invocation's full SHA (or a recorded short-ref -> full-SHA resolution), identity\u002Fmodel,\nand tool-routing metadata. Accept only the critic's native `No findings.` or structured finding\noutput -- never manufacture `Checked:` evidence. A delegated worker's critic does not replace\nthe parent-owned final critic. A parent driver consumes its own final-HEAD critic; it does not\nhand that responsibility to itself or repeat an unchanged review merely to change its label.\n\n- Fix every real blocking finding, rerun the affected gate, and push the follow-up\n- Every change to HEAD invalidates the critic and both review axes. Renew both axes and every permitted critic on the final SHA; a restricted worker leaves the parent critic explicitly PENDING\n- Record reviewer identities\u002Fmodels, reviewed SHA, and `Checked:`\u002F`Findings:` reports for the two axes; record the critic's original SHA-bound invocation, tool-routing metadata, native output, and each finding disposition\n- Document a concrete rationale for any retained judgement finding\n\n## 8. Open the PR\n\n`gh pr create --title \"\u003Ccommit subject>\" --body-file \u003Ctmpfile>`. Write the body to a file in the\nscratchpad; do not fight shell quoting.\n\nBody, in order:\n\n- `Closes #\u003CN>.` (or `Fixes #\u003CN>.`)\n- `Changes:` plus bullets -- one concrete change each, backtick every identifier, path, and\n  dotted module path\n- `Verification:` plus prose bullets carrying REAL command output. Fence it when long. Test\n  counts, coverage numbers, and actual failure transcripts, not \"tests pass\"\n- Exact-HEAD Standards and Spec receipts with `Checked:`\u002F`Findings:`, plus the permitted critic's original SHA-bound invocation, tool-routing metadata, native output, and finding dispositions; otherwise `Parent critic: PENDING` with concrete review handles\n- The continuation record: PR URL, final SHA, concrete CI run IDs or commands, and its owner. A delegated worker names the parent; a parent driver keeps ownership\n- The `🤖 Generated with [Claude Code](https:\u002F\u002Fclaude.com\u002Fclaude-code)` footer\n\nNever: `## Summary`, `## Test plan`, `## Root cause`, checkbox lists, or an invented body for a\nchange whose title already says everything. A title-only PR is a fine default for something\ngenuinely routine -- but a shipped issue almost always earns a body.\n\nMark it draft (`--draft`) only when the branch genuinely depends on unmerged work, and say what\nit is waiting on.\n\n## 9. Handoff and cleanup\n\nWhich role are you? A PARENT driver is the agent the user asked directly; a DELEGATED worker was\nspawned by a parent for this issue. Never hand off to yourself.\n\n- Before changing the PR HEAD, disable any armed auto-merge with `gh pr merge --disable-auto \u003CN>` and verify it is off. Renew the critic and both axes after any HEAD change\n- Do not require a rebase merely because the base advanced. Update only for a functional dependency or actual conflict; release\u002Fdeploy work separately requires the frozen combined gate\n- Never delegate passive watching or waiting to a watcher agent\n- Parent driver: for admission, protection, merge and terminal monitoring, follow `\u002Fskill:get-it-merged` steps 3-4 as a one-PR train. That shared procedure requires effective non-bypassable protection before auto-merge; otherwise it keeps auto-merge off, completes exact-HEAD CI and merges explicitly. Do not duplicate or weaken it here\n- Parent completion: continue until this PR is `MERGED`, or a genuine external blocker has a named owner and an armed continuation monitor. Queued CI, ordinary setup, tests and review fixes are unfinished work, not successful completion\n- Delegated worker: keep auto-merge off, do not merge or arm it. Once the substantive work is done, return the PR URL, final SHA, exact review handles, and concrete CI run IDs or monitor command to the parent, once. Never declare the overall task done\n- Do NOT remove the worktree before the PR lands. The follow-up is `git worktree remove \u003Cpath> && git -C \u003Crepo> worktree prune` once it merges\n\n## 10. Report\n\nShort. Issue -> branch -> PR URL -> gate result -> review outcome -> the worktree cleanup\nfollow-up. No closing summary paragraph, no restating the plan back.\n\n## Guardrails\n\n- Gate cannot be made green: stop and report. Do not ship it\n- Never force-push the default branch; `--force-with-lease` on your own branch only\n- Never merge past failing checks by hand or bypass protection\n- The repo's `CLAUDE.md` outranks this file on every conflict\n","# ship-issue\n\nTake a GitHub issue from \"here is the URL\" to a reviewed PR in an isolated worktree. The parent\nowns the final critic, native CI monitoring, and protected merge outcome; a delegated\nworker hands those back with concrete handles.\n\nThe repo's own `CLAUDE.md` \u002F `AGENTS.md` OVERRIDES everything below. Read it first (step 3) and\nlet it win on gate commands, coverage bars, layout, and style. This file is the procedure, not\nthe house rules.\n\nAnything you emit -- commit messages, PR bodies, review comments, the final report -- follows\nthe user's configured writing style (their global agent instructions, when they have any). The\ndefault style, absent other instructions: bare colon-terminated lead-ins plus `-` bullets, NO\nmarkdown headers, no checkbox lists, `--` never em-dashes, backtick every identifier and path.\nThe headers in *this* file are instructions to you, not a template.\n\n## 1. Resolve the issue\n\nAccept a full URL, `#128`, or a bare `128`. From a URL, pull owner\u002Frepo too -- it may not be the\ncwd repo.\n\n- `gh issue view \u003CN> --json number,title,body,labels,state,comments`\n- Read the comments, not just the body. Prior design context and scope cuts usually live there\n- STOP and report if: the issue is closed, or `gh pr list --search \"\u003CN>\"` shows an open PR\n  already addressing it. Do not double-ship\n- If two readings of the issue produce materially different work, ask before implementing. If\n  it is merely underspecified, make the call a careful colleague would make and say which\n  assumption you took\n\n## 2. Worktree\n\nNever work in the user's checkout. One issue, one worktree.\n\n- `git -C \u003Crepo> fetch origin` then `git -C \u003Crepo> worktree prune` (stale `prunable` entries\n  accumulate)\n- Branch: `\u003Cprefix>\u002Fissue-\u003CN>`. `\u003Cprefix>` is the repo's documented branch-prefix convention\n  (check `AGENTS.md` \u002F `CONTRIBUTING.md` and recent branches), else the operator's GitHub login\n  (`gh api user --jq .login`). Append a short kebab slug from the title when the bare number is\n  ambiguous or the repo has several open issues in the same area -- e.g.\n  `\u003Cprefix>\u002Fissue-103-flaky-port-race`\n- Path: a SIBLING of the repo root, `\u003Cparent-of-repo>\u002Fissue-\u003CN>`. For\n  `\u002Fwork\u002Fplugins\u002Fexample-repo` that is `\u002Fwork\u002Fplugins\u002Fissue-\u003CN>`\n- `git -C \u003Crepo> worktree add -b \u003Cbranch> \u003Cpath> origin\u002F\u003Cdefault-branch>`\n- Do NOT use the `EnterWorktree` tool. It does not honor this layout\n- Every subsequent command runs with `\u003Cpath>` as cwd. Pass it explicitly (`git -C`, `make -C`,\n  absolute paths) rather than relying on shell state\n\n## 3. Read the repo's rules\n\n- Root `CLAUDE.md` \u002F `AGENTS.md`, plus any directory-scoped ones near the files you will touch\n- `Makefile` targets -- that is where the real gate is defined\n- `CONTRIBUTING.md`, `CHANGELOG.md` (does the repo keep one? Keep a Changelog format?)\n\nNote the hard rules explicitly before writing code. They are the ones the reviewers will check\nagainst, and the ones that make a PR bounce. Typical shapes: no inline waivers (`noqa`,\n`type: ignore`), a coverage floor, modules that must stay import-light, version strings that\nlive in more than one file, a required changelog entry.\n\n## 4. Implement\n\nOrdinary work, scoped to the issue. Tests by default -- the repo's existing test layout tells\nyou where they go and what style they are in.\n\n- Match the surrounding code's idiom, naming, comment density, and docstring form\n- Update the changelog if the repo keeps one\n- Update docs if the change is user-facing and the repo has a docs tree\n- Do not widen scope. If you find an adjacent bug, note it for the report; fix it only if the\n  change is unshippable without it, and say so in the PR body\n\n## 5. Gate -- before review, not after\n\nRun the repo's real gate and capture the ACTUAL output. It becomes the `Verification:` bullets.\n\n- `make all` when the `Makefile` defines it. Otherwise the closest equivalent: format, lint,\n  type check, tests\n- `uv run prek run --all-files` (or `pre-commit run --all-files`) when the repo has a\n  `.pre-commit-config.yaml`. Local hooks gate commits; a manual run catches what you would\n  otherwise discover at push time\n- Lockfile check and build if the repo has them (`uv lock --check`, `uv build`)\n\nRed gate means do not proceed. Fix it, or stop and report why it cannot be made green. Never\nship on a gate you did not actually run -- \"the imports resolved\" is not evidence.\n\n## 6. Commit and push\n\n- Subject: capitalized imperative, no trailing period, no conventional-commit prefix (no\n  `feat:` \u002F `fix:` \u002F `chore:`)\n- Body only when the subject cannot carry it. Then `Changes:` plus `-` bullets, one concrete\n  change each, phrased \"Verb the `thing`\"\n- Keep the `Co-Authored-By: Claude ...` footer. Attribution is a footer, not a writing style --\n  the body above it reads like the user\n- `git push -u origin \u003Cbranch>`\n- Never `git push --force` to the default branch. Force-push only your own issue branch, and\n  only with `--force-with-lease`\n\n## 7. Review round -- exact final HEAD\n\nAfter the gate, use `\u002Fskill:code-review` for the separate Standards and Spec axes. Run one dedicated\n`critic` only when your actual allowed-subagent list permits it. A delegated worker restricted to\n`code-reviewer` opens the PR and returns the original axis reports and concrete handles with\n`Parent critic: PENDING`. Keep permissions unchanged. The parent must run its independent\nfinal-HEAD critic BEFORE merge admission, even if a permitted worker ran one.\n\nWhoever runs a critic spawns `Agent(subagent_type: \"critic\")` with no `model`; its `agentModels`\ntier picks the model. Only when the issue is design-level (new module or public interface,\nconcurrency, persistence or wire format, auth), add a second\n`Agent(subagent_type: \"critic\", model: \"@frontier\")`. Name tiers, never model ids. If either route\nis quota-parked, wait; do not silently substitute a model or another tier.\n\nThe shared skill selects parent background versus delegated blocking calls, supplies both full SHAs\nand the original whole-PR range, and renews it after a HEAD change. Pass the issue\u002Fspec and repo\nrules; do not use the ambiguous `\u002Fcode-review` workflow command.\n\nThe critic is supplementary, never a substitute for either axis. It is read-only and already\ncarries the refute-before-report rule, so name the final diff and issue only. Its receipt preserves\nthe original invocation's full SHA (or a recorded short-ref -> full-SHA resolution), identity\u002Fmodel,\nand tool-routing metadata. Accept only the critic's native `No findings.` or structured finding\noutput -- never manufacture `Checked:` evidence. A delegated worker's critic does not replace\nthe parent-owned final critic. A parent driver consumes its own final-HEAD critic; it does not\nhand that responsibility to itself or repeat an unchanged review merely to change its label.\n\n- Fix every real blocking finding, rerun the affected gate, and push the follow-up\n- Every change to HEAD invalidates the critic and both review axes. Renew both axes and every permitted critic on the final SHA; a restricted worker leaves the parent critic explicitly PENDING\n- Record reviewer identities\u002Fmodels, reviewed SHA, and `Checked:`\u002F`Findings:` reports for the two axes; record the critic's original SHA-bound invocation, tool-routing metadata, native output, and each finding disposition\n- Document a concrete rationale for any retained judgement finding\n\n## 8. Open the PR\n\n`gh pr create --title \"\u003Ccommit subject>\" --body-file \u003Ctmpfile>`. Write the body to a file in the\nscratchpad; do not fight shell quoting.\n\nBody, in order:\n\n- `Closes #\u003CN>.` (or `Fixes #\u003CN>.`)\n- `Changes:` plus bullets -- one concrete change each, backtick every identifier, path, and\n  dotted module path\n- `Verification:` plus prose bullets carrying REAL command output. Fence it when long. Test\n  counts, coverage numbers, and actual failure transcripts, not \"tests pass\"\n- Exact-HEAD Standards and Spec receipts with `Checked:`\u002F`Findings:`, plus the permitted critic's original SHA-bound invocation, tool-routing metadata, native output, and finding dispositions; otherwise `Parent critic: PENDING` with concrete review handles\n- The continuation record: PR URL, final SHA, concrete CI run IDs or commands, and its owner. A delegated worker names the parent; a parent driver keeps ownership\n- The `🤖 Generated with [Claude Code](https:\u002F\u002Fclaude.com\u002Fclaude-code)` footer\n\nNever: `## Summary`, `## Test plan`, `## Root cause`, checkbox lists, or an invented body for a\nchange whose title already says everything. A title-only PR is a fine default for something\ngenuinely routine -- but a shipped issue almost always earns a body.\n\nMark it draft (`--draft`) only when the branch genuinely depends on unmerged work, and say what\nit is waiting on.\n\n## 9. Handoff and cleanup\n\nWhich role are you? A PARENT driver is the agent the user asked directly; a DELEGATED worker was\nspawned by a parent for this issue. Never hand off to yourself.\n\n- Before changing the PR HEAD, disable any armed auto-merge with `gh pr merge --disable-auto \u003CN>` and verify it is off. Renew the critic and both axes after any HEAD change\n- Do not require a rebase merely because the base advanced. Update only for a functional dependency or actual conflict; release\u002Fdeploy work separately requires the frozen combined gate\n- Never delegate passive watching or waiting to a watcher agent\n- Parent driver: for admission, protection, merge and terminal monitoring, follow `\u002Fskill:get-it-merged` steps 3-4 as a one-PR train. That shared procedure requires effective non-bypassable protection before auto-merge; otherwise it keeps auto-merge off, completes exact-HEAD CI and merges explicitly. Do not duplicate or weaken it here\n- Parent completion: continue until this PR is `MERGED`, or a genuine external blocker has a named owner and an armed continuation monitor. Queued CI, ordinary setup, tests and review fixes are unfinished work, not successful completion\n- Delegated worker: keep auto-merge off, do not merge or arm it. Once the substantive work is done, return the PR URL, final SHA, exact review handles, and concrete CI run IDs or monitor command to the parent, once. Never declare the overall task done\n- Do NOT remove the worktree before the PR lands. The follow-up is `git worktree remove \u003Cpath> && git -C \u003Crepo> worktree prune` once it merges\n\n## 10. Report\n\nShort. Issue -> branch -> PR URL -> gate result -> review outcome -> the worktree cleanup\nfollow-up. No closing summary paragraph, no restating the plan back.\n\n## Guardrails\n\n- Gate cannot be made green: stop and report. Do not ship it\n- Never force-push the default branch; `--force-with-lease` on your own branch only\n- Never merge past failing checks by hand or bypass protection\n- The repo's `CLAUDE.md` outranks this file on every conflict\n",{"name":5,"description":7,"argument-hint":24},"\u003Cissue-url-or-number> [extra instructions]","main","9ca373de7213ce33ac1c383b5706b72feb82bac9","packages\u002Fpreset\u002Fskills\u002Fship-issue",1,"https:\u002F\u002Fgithub.com\u002Fnredd\u002Fpi-harness","https:\u002F\u002Fgithub.com\u002Fnredd","DV Infra & Methodology @ QCOM | Caltech '19","2026-11-15 12:27:17",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add nredd\u002Fpi-harness --skill ship-issue",{"tool":39,"command":40},"bunx","bunx skills add nredd\u002Fpi-harness --skill ship-issue",{"tool":42,"command":43},"pnpm","pnpm dlx skills add nredd\u002Fpi-harness --skill ship-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnredd\u002Fpi-harness\u002Fblob\u002Fmain\u002Fpackages\u002Fpreset\u002Fskills\u002Fship-issue\u002FSKILL.md",true,[],[48,55,62],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7F0CCGWM47A2796Q6FH8AV8","get-it-merged","Land a requested set of open PRs as a dependency-aware merge train: the parent reviews, arms protected auto-merge, watches each terminal outcome with a native monitor, and advances until the list is merged or genuinely blocked. Use when multiple PRs are open in one repo and the user wants them merged.","https:\u002F\u002Fgithub.com\u002Fnredd\u002Fpi-harness\u002Fblob\u002Fmain\u002Fpackages\u002Fpreset\u002Fskills\u002Fget-it-merged\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7F0C8KTXWQ463FR653N783M","coding-like-redd","Redd's Python and Rust coding standards -- tooling (uv\u002Fruff\u002Fty; cargo\u002Fclippy\u002Fnextest), code style rules, error\u002Flogging\u002Fsubprocess conventions, and required-project-file templates (including Makefiles). Load whenever writing, reviewing, editing, or scaffolding Python or Rust code, or asked about Redd's coding standards, in ANY project.","https:\u002F\u002Fgithub.com\u002Fnredd\u002Fpi-harness\u002Fblob\u002Fmain\u002Fpackages\u002Fpreset\u002Fskills\u002Fcoding-like-redd\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7F0C3AZT3FSYY70WBHJZZD9","code-review","Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue\u002Fspec asked for?). Runs both reviews in parallel read-only `code-reviewer` sub-agents through the configured review route and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".","https:\u002F\u002Fgithub.com\u002Fnredd\u002Fpi-harness\u002Fblob\u002Fmain\u002Fpackages\u002Fpreset\u002Fskills\u002Fcode-review\u002FSKILL.md",[],[]]