[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F35G8WVAFT16VHH62EBVP1":3,"skill-same:01M7F35G8WVAFT16VHH62EBVP1":60},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7F35G8WVAFT16VHH62EBVP1","pr-fixup",null,"Wait for CI and automated reviews on a PR, fix valid failures and comments, disposition every review thread, verify, and push in the primary conversation.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fpr-fixup\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: pr-fixup\ndescription: Wait for CI and automated reviews on a PR, fix valid failures and comments, disposition every review thread, verify, and push in the primary conversation.\n---\n\n# PR Fixup\n\nUse this workflow directly in the user-started primary conversation. Do not\nlaunch a verifier, implementer, or other remediation subagent. A read-only\n`pr-poller` is the sole exception: launch it only when the user explicitly asks\nto wait for or monitor PR updates. For a cost-controlled workflow, the user may\nswitch the same conversation to the lower-cost implementation\u002Ftest model before\nstarting CI remediation.\n\nUse `gh` by default; auth or transport errors leave state unknown, never clean.\nIf connector tools are available, use structured PR\u002Fcheck\u002Fthread data; avoid\ndumping full HTML\u002Fdiffs. Map GraphQL thread IDs to REST comment IDs before\nreplies, and refresh current-head state after pushes and review aggregation.\n\n## Pipeline\n\nCreate a visible checklist:\n\n1. Gather PR state\n2. Resolve an authorized PR merge conflict\n3. Fix failing CI checks\n4. Triage every review thread\n5. Apply valid fixes and record every disposition\n6. Commit, rerun affected checks, and push\n7. Re-check the new head\n8. Report\n\n## 1. Gather PR State\n\nBefore the first GitHub helper call, request any runtime network approval that\nthe environment requires. If access is denied, cancelled, or interrupted, stop\nthe workflow permanently; retry only transient fetch failures after access is\napproved.\n\nRun `scripts\u002Fpr-state --summary \u003CPR>` once. Record the current-head check,\nreview, and PR-delivery fields described in\n`references\u002Freview-evidence.md`. For a cross-repository PR, use only the\nreported delivery fields as the push target; do not infer it from a local\n`fork` or `contributor` remote. Load that reference for exact-head review\nclassification, authentication fallbacks, and hidden-thread handling. Inspect\nmergeability separately through `references\u002Fmerge-conflicts.md`.\n\nIf the fresh mergeability query reports `mergeable=CONFLICTING` or\n`mergeStateStatus=DIRTY`, stop CI and review triage. This is an actionable PR\nblocker, not a clean or report-only terminal state. Load\n`references\u002Fmerge-conflicts.md`. If the user has explicitly authorized PR\nfixup or conflict resolution, resolve the conflict now (prefer a merge of the\nfresh base unless the user requests a rebase), verify the result, push it, and\nrestart this section with a new PR-state snapshot. If authorization is absent,\nreport the conflict and ask for it before mutating the branch. Do not triage\ncomments or checks against a conflicted head.\n\nFor pending CI, wait with `scripts\u002Fpr-await \u003CPR>`. It blocks below the\nconversation and prints one report when every check is terminal, so a wait of\nany length costs a single round-trip. Do not re-run `scripts\u002Fpr-state\n--summary` on a timer instead: each snapshot is a separate model turn that\nre-reads the whole context, and waiting is only about 6% of what such a turn\nactually does.\n\nDefault `--mode all-terminal` is the cost-correct choice and returns only when\nno check is pending, so every failure arrives in one report and is fixed in one\npass. It is also the correct choice for a reason unrelated to cost: a failed job\ncan be visible while its parent workflow is still running, so an early return\nreports a partial failure set. Use `--mode first-failure` only when the user\nwants the first failure interactively; it costs an extra full CI cycle per\nfailure. Pass `--deadline-min` for a user-stated limit; on exit 2 report the\nnamed pending checks as \"CI in progress.\"\n\nRead its exit code rather than re-deriving state: 0 clean, 1 terminal with\nfindings, 2 deadline with checks still pending, 3 blocked. Exit 3 covers every\ncase where a clean answer cannot be trusted: the PR merged or closed, a workflow\nneeds approval, access was lost, the merge-state query failed, the snapshot\nreported `errors` or a null unresolved-thread count, or the host toolchain\ncannot run `pr-state` correctly. Never downgrade an exit 3 to \"probably clean.\"\n\nExit 1 counts blocking reviews, not only threads: a current-head\n`CHANGES_REQUESTED` review can exist with no unresolved thread attached.\n\nEvery report records the jq and bash versions it ran under. That is provenance,\nnot a gate: `pr-state` used to fail silently on jq 1.6 and on the bash 3.2 that\nmacOS ships as `\u002Fbin\u002Fbash`, both of which made a dirty PR look clean, and both\nare fixed at the source. What guards against a degraded `pr-state` now is the\nsnapshot itself, which is stronger than any version check: a summary reporting\n`errors`, one whose unresolved-thread count is null, and one that does not parse\nare all treated as unknown rather than clean. A blocked report on an old\ntoolchain adds a note naming it as a possible cause. A push during the wait\nrestarts the gate against the new head and is reported.\n\nDo not use interactive `gh pr checks --watch` in the primary conversation: its\nTTY redraws make captured output unusable. Use the read-only `pr-poller` only\nwhen the user explicitly asked to wait or monitor and `pr-await` is unavailable.\nTreat a poller's unresolved\u002Fpending snapshot as provisional: it can predate a\nprimary-session push or thread resolution. Re-run `scripts\u002Fpr-state --summary\n\u003CPR>` at the current head before acting on it or declaring completion.\nIf a job remains pending beyond the workflow's configured timeout, or its status\nconflicts with the GitHub UI\u002FAPI, query the exact job with\n`gh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Factions\u002Fjobs\u002F\u003Cjob_id>` (or inspect the run with\n`gh run view \u003Crun_id>`) before calling CI hung or changing code. Treat the direct\nresult as current-head evidence only after its `head_sha` matches\n`checks_head_sha`; otherwise report the result as stale or unknown.\n\nFor a cross-repository PR whose current-head snapshot is unexpectedly sparse,\ninspect `approval_required_runs`. A current-head workflow with\n`conclusion=action_required` is blocked verification, not green or skipped CI.\nOnly after the user authorizes PR fixup, approve the exact run with\n`gh api --method POST repos\u002F\u003Cbase-owner>\u002F\u003Cbase-repo>\u002Factions\u002Fruns\u002F\u003Crun-id>\u002Fapprove`,\nthen re-run the summary and require jobs to materialize before polling. `gh run\napprove` is not a valid command.\n\nTreat the state as clean only when the current head has no failed or pending\nchecks, no merge conflict, no blocking review (an active `CHANGES_REQUESTED`\nor a review blocked at the exact current head), no unresolved review thread, no\nactionable issue comment, and qualifying exact-head semantic evidence where PR\ndelivery requires it.\n\n## 2. Fix CI Failures\n\nBefore changing code, confirm every reported failed check, its `run_id`, and\nthe parent workflow\u002Fjob status. A failed job can be visible while its workflow\nis still in progress; confirm its conclusion and failing step before treating\nit as reproducible code evidence. Use\n`scripts\u002Frun-quiet gh-run -- gh run view \u003Crun-id> --log-failed` so large logs do\nnot flood the conversation. If it returns only GitHub request\u002Ftransport lines\nor no failure text, treat logs as unavailable and, after terminal state, use\n`scripts\u002Fpr-state --job-log \u003Cjob_id>`. For temporary gaps or aggregate-only\nlogs, use the same fallback; it handles plain-text and ZIP responses and emits\nbounded context. Follow `references\u002Fci-troubleshooting.md`. Reproduce the exact\nfailed command where possible; CI-specific Go lint often needs\n`golangci-lint run .\u002F... --new-from-rev=\u003Cbase> --timeout=5m`.\n\nIf CI reports files or commits outside the PR diff, or a stale base SHA, resolve\nthe authoritative base repository, ref name, and current base SHA from PR\nmetadata. Fetch that ref from an explicit base remote, verify its tip matches\nthe reported SHA, and compare `git merge-base HEAD \u003Cbase-remote>\u002F\u003Cbase-ref>`\nwith `git diff \u003Cbase-remote>\u002F\u003Cbase-ref>...HEAD`; do not assume `origin\u002F\u003Cbase>`\nwhen `origin` points to a fork. Inspect the parent workflow\u002Frun to determine\nwhether a newer base commit caused the failure before changing product or docs\ncode. If the fix is already upstream, update or rebase the branch only when\nauthorized, rerun affected checks, and invalidate all prior exact-head evidence.\n\nFor unfamiliar, infrastructure, or E2E failures, load\n`references\u002Fci-troubleshooting.md` before changing code.\nAlso load it for unexpected zero-duration or no-op manual-review runs: event\nand workflow provenance can explain them without a product-code change.\n\nAn explicit request to run `pr fixup` owns every failed required check on the\ncurrent head. Never stop by calling a failure \"unrelated\" only because its\nfiles are outside the PR diff. Reproduce each leaf failure with retries\ndisabled, inspect its artifacts and shared fixtures\u002Fcleanup, and fix every\nvalid product, test, fixture, cleanup, or CI-contract defect it exposes. A\ndependent aggregate failure does not replace its leaf failures: trace the\naggregate to all failed jobs, fix the underlying failures, and wait for the\naggregate checks to rerun. If concrete evidence proves a failure is external\nafter this investigation, report the exact job\u002Flog\u002Freproduction evidence and\nkeep the PR blocked; do not call it ready while a required check is failed.\n\nFix with `\u002Ftdd` or `\u002Fe2e` as applicable, run focused checks, and keep each\nremediation scoped to the reported failure. Do not suppress a failure or mark a\ncheck clean without fresh evidence.\n\nIf a reproducible failure is outside the PR diff, compare the failing\nassertion with the current implementation and concurrent or sibling PRs before\nediting. If it is a stale test expectation, the smallest valid remediation may\nbe a test-only assertion update: keep it limited to the reported failure, run\nthe focused test, and call out that scope. Do not change unrelated production\nbehavior or duplicate a larger sibling change.\nWhen a remediation changes a documented behavior or contract, update the\nauthoritative spec\u002Fguidance, plan, and task file when present; commit docs and\ncode together, keep regression tests and verification commands aligned, and\nre-check the documentation before completion. Record why no update is needed\nwhen the behavior remains internal.\n\n## 3. Triage And Address Reviews\n\nUse `scripts\u002Fpr-resolve list \u003CPR>` to obtain unresolved threads. Its previews\ncan be truncated, so expand every listed review thread with\n`scripts\u002Fpr-resolve show \u003CPR> \u003Cthread_id>` before deciding how to handle it.\nUse `scripts\u002Fpr-state --comment \u003Ccomment_id>` only for a flat comment view when\na thread context is not available. Validate against the current head, the spec,\nand existing architecture before editing or replying.\n\nEvery unresolved thread requires an explicit disposition, regardless of its\nauthor, bot identity, visibility, or apparent severity. Record exactly one of\nthese dispositions:\n\n- `actionable`: make the valid code or test change, verify it, cite the\n  resulting commit in the reply, and resolve the thread when writes are\n  authorized.\n- `already addressed`: verify the current implementation or an existing commit,\n  explain where it is addressed, and resolve the thread when writes are\n  authorized.\n- `informational` or `optional`: make no code change, acknowledge the information\n  or suggestion in a reply, and resolve it when complete cleanup is requested.\n- `invalid`: do not make an invalid code change or silently ignore the finding;\n  reply with concrete reasoning grounded in the code, spec, or architecture,\n  then resolve it only after that pushback is posted and writes are authorized.\n\nA classification is not a disposition. A thread is not complete merely because\nit was called optional, informational, already addressed, or invalid. GitHub\nreplies and thread resolution are external writes. A request such as \"complete\ncleanup\", \"clean up all review threads\", or \"leave no threads unresolved\"\nexplicitly authorizes a concise reply and resolution for every unresolved\nthread, including informational, optional, and invalid findings. A request to\naddress selected comments authorizes replies and resolution only for those\nselected threads. A review-only request authorizes no writes. When writes are\nnot authorized, record every disposition, report the still-unresolved thread,\nand do not declare the PR clean.\n\nFor code changes, push the fix and pass targeted verification before replying\nand resolving. For non-code dispositions, verify the current head first, then\nuse the atomic helper path\n`scripts\u002Fpr-resolve reply \u003CPR> \u003Ccomment_id> \u003Cthread_id> --body-file \u003Cpath>` to\nreply, resolve, and react in one operation when the body contains Markdown or\nshell metacharacters. For short plain-text bodies, a safely quoted argument is\nacceptable. Never interpolate review text into an unquoted shell command or\nuse backticks in the command itself. After the helper returns, re-fetch the\nthread and verify the posted reply body and resolved state before treating the\ndisposition as complete.\nThen rerun\n`scripts\u002Fpr-resolve list \u003CPR>` and the exact-head `scripts\u002Fpr-state --summary\n\u003CPR>` check before reporting.\n\nFor an ordering or concurrency finding, trace the complete producer → event-bus\ntransport → gateway\u002Fclient path. Sequential publishes do not prove delivery\norder when a remote bus uses separate subscriptions; consolidate one stream or\nadd sequence-aware buffering when order is contractual, and cover both the\ntransport boundary and local emulator.\n\nWhen feedback says an action must remain reachable, add and run a regression at\nthe legal minimum width. Verify the actual hit target (for example,\n`elementFromPoint()` at the control center) and clickability, not only\n`toBeVisible`, before pushing.\n\n## 4. Commit, Verify, Push\n\nCommit through `\u002Fcommit`, then rerun only the unit, integration, or E2E command\naffected by the remediation. Push when that targeted check passes for the exact\ncurrent `HEAD`. For a cross-repository PR, push the exact current `HEAD` to the\nsummary's authoritative head repository and ref only when\n`pr.maintainer_can_modify` is true. Re-fetch the PR afterward and require its\n`pr.head_ref_oid` to equal local `HEAD`; an upstream remote comparison is not\nsufficient. Run broad `\u002Fverify` only if the user explicitly requests it or the\nPR\u002FCI finding requires it.\nAfter every push, also run a fresh\n`gh pr view \u003CPR> --json baseRefName,headRefOid,mergeable,mergeStateStatus` (or\nequivalent) at that pushed head. Require `headRefOid` to equal local `HEAD` and\nconfirm `mergeable` is not `CONFLICTING` and `mergeStateStatus` is not `DIRTY`;\n`scripts\u002Fpr-state --summary` does not include mergeability.\n\nImmediately before a remediation commit or push—and again after long-running\nremediation—refresh PR state. Require the PR to remain open and its head ref to\nmatch the local branch. Before a push, compare the remote head OID with the\nlocal upstream tip; after the push, require the PR head OID to equal local\n`HEAD`. If the PR merged or closed, do not recreate its deleted branch with a\nstale push: preserve the local fix and ask before creating a clean follow-up.\n\nAfter any rebase or force-push, fetch the PR base and compare local `HEAD`, the upstream tip, and `pr.head_ref_oid`; rerun affected checks.\nA rebase onto a newer base invalidates prior evidence: rerun the exact failed\ncommand and any package-level gate required by whole-file rules (for example\nmax-lines). Then rerun `scripts\u002Fpr-resolve list \u003CPR>` and `scripts\u002Fpr-state --summary \u003CPR>`; distinguish stale\u002Fcurrent\nfailures and report pending checks separately. Use `--force-with-lease`, never an unconditional force-push.\nIf the rebase or conflict resolution touched `AGENTS.md`, `CLAUDE.md`, or a\nskill\u002Freference file, run the shared harness validation in\n`.agents\u002Fskills\u002Fharness-improvement\u002Freferences\u002Fvalidation.md` before pushing.\n\n## 5. Re-check\n\nAfter every push, re-fetch current-head state and run\n`scripts\u002Fpr-resolve list \u003CPR>` (and `show` for any thread you may answer), then\n`scripts\u002Fpr-state --summary \u003CPR>` again for the new head. For explicit\nconsolidation, verify the target head before commenting\u002Fclosing the superseded\nPR; preserve its branch unless deletion is requested. Automated reviewers may\nresolve or replace threads; do not reply to or resolve a thread that fresh state\nreports as resolved. Before replying to a pre-push thread, run\n`scripts\u002Fpr-resolve show \u003CPR> \u003Cthread_id>`; if it reports `resolved: true` (often\nwith an `Addressed in commit ...` marker), record the thread as auto-resolved and\ndo not post a duplicate reply. Continue replying\u002Fresolving only for `resolved: false` threads, including hidden unresolved threads.\nTreat each fresh summary as a new review-evidence snapshot: inspect every\nnon-empty body in `review_evidence.exact_current_head_reviews[]`, even when\n`unresolved_review_thread_count=0` and `scripts\u002Fpr-resolve list` is empty.\nClassify current-head review bodies and top-level bot\u002Fissue comments before\ndeclaring the PR clean; empty thread and issue-comment counts are insufficient.\nTreat a non-empty `hidden_unresolved_threads` value in that fresh snapshot as a\nmandatory hidden-thread gate: expand and disposition each hidden thread, then\nrun `scripts\u002Fpr-resolve list \u003CPR>` again after the refresh and immediately\nbefore reporting.\nRequire `checks_head_sha` to match that head, report pending checks separately\nfrom failures, and rerun `scripts\u002Fpr-resolve list \u003CPR>` before declaring the\nPR clean. The final predicate must also require\n`hidden_unresolved_threads=[]`; do not require filtered and unresolved counts to\nbe equal because the filtered count includes resolved threads. Treat prior review\nevidence as stale. When the user authorized thread writes, every unresolved\nthread still needs an explicit reply and resolution matching its disposition.\nA duplicate or stale bot thread needs the same treatment once current source\nproves the finding is already fixed, including a thread surfaced only in\n`hidden_unresolved_threads`; only current-head actionable threads drive code\nchanges. Declare the PR clean only when the\nexact-current-head review classification reports no unaddressed findings,\n`checks_snapshot_complete=true`, `failed_checks=[]`, `pending_checks=[]`,\n`approval_required_runs=[]`, `actionable_issue_comment_count=0`,\n`unresolved_review_thread_count=0`, `hidden_unresolved_threads=[]`, there is no\nmerge conflict, and\n`scripts\u002Fpr-resolve list \u003CPR>` is empty. Within\nthe user's monitoring limit, continue checking after resolutions until automated\nreview jobs are terminal; otherwise report the exact pending check names.\n\nIf the user explicitly requested a persistent Kandev plan update and the task\nhas an external Kandev plan, call `get_task_plan_kandev` before fixup and\n`update_task_plan_kandev` after fixup with the remediation commit, final\nexact-head check counts, resolved-thread state, and mergeability. Without that\nauthorization, report the plan update as pending and do not invoke Kandev task\nor session APIs. Batch plan\u002Ftask synchronization into the final documentation\ncommit. Record the prior head's fixup evidence before a plan commit\u002Fpush: that\npush restarts CI and invalidates the snapshot. For tracked `docs\u002Fplans\u002F**`\nartifacts, keep prose head-agnostic and record remediation scope\u002Flocal\nverification before that commit; then rerun `scripts\u002Fpr-state --summary` and\n`scripts\u002Fpr-resolve list` for the new head and report its pending checks\nseparately. Mark prior current-head claims historical\u002Fsuperseded when a new\nhead replaces them; report only the latest head's SHA, CI\u002Freview counts, and\nmergeability. Do not leave planned verification marked unstarted after it has run.\n\nBefore declaring fixup complete, verify `git status --short` is clean,\n`git rev-parse HEAD` equals `git rev-parse @{upstream}`, the PR head equals\nlocal `HEAD`, and the fresh mergeability state is not conflicting. Do not call\nthe PR clean from CI\u002Freview counts alone when the worktree or remote tip still\ndiffers.\n\nThe phrase \"ready to merge\" is reserved for a fresh current-head snapshot\nwith every required check successful or explicitly skipped, no pending or\nfailed leaf or aggregate check, no unresolved review thread, no merge conflict,\nand the local, upstream, and PR head OIDs aligned. A clean local reproduction\ndoes not waive a failed remote check; push the remediation and re-check the\nnew head first.\n\n## 6. User-Requested Merge\n\nMerge only after the user explicitly asks and the current-head state is clean.\nFrom a linked worktree, run `gh pr merge \u003CPR> --squash` without\n`--delete-branch`: that flag can attempt a local checkout of the base branch\nand fail when another worktree owns it, even after the remote merge succeeds.\nReport the remote merge separately. Delete a remote or local branch only when\nrequested and through a worktree-safe cleanup flow.\n\n## Guardrails\n\n- Do not create Kandev subtasks unless the user explicitly asks for task\n  tracking.\n- Do not use native delegation or a full-history context fork to poll CI.\n- Do not push, post comments, or resolve threads when the user asked for review\n  only.\n- Do not silently dismiss an invalid finding; every invalid thread needs a\n  concrete pushback disposition, and an authorized complete cleanup must post\n  that explanation before resolving it.\n- Do not proceed with an unverified PR when mandatory verification is blocked.\n","# PR Fixup\n\nUse this workflow directly in the user-started primary conversation. Do not\nlaunch a verifier, implementer, or other remediation subagent. A read-only\n`pr-poller` is the sole exception: launch it only when the user explicitly asks\nto wait for or monitor PR updates. For a cost-controlled workflow, the user may\nswitch the same conversation to the lower-cost implementation\u002Ftest model before\nstarting CI remediation.\n\nUse `gh` by default; auth or transport errors leave state unknown, never clean.\nIf connector tools are available, use structured PR\u002Fcheck\u002Fthread data; avoid\ndumping full HTML\u002Fdiffs. Map GraphQL thread IDs to REST comment IDs before\nreplies, and refresh current-head state after pushes and review aggregation.\n\n## Pipeline\n\nCreate a visible checklist:\n\n1. Gather PR state\n2. Resolve an authorized PR merge conflict\n3. Fix failing CI checks\n4. Triage every review thread\n5. Apply valid fixes and record every disposition\n6. Commit, rerun affected checks, and push\n7. Re-check the new head\n8. Report\n\n## 1. Gather PR State\n\nBefore the first GitHub helper call, request any runtime network approval that\nthe environment requires. If access is denied, cancelled, or interrupted, stop\nthe workflow permanently; retry only transient fetch failures after access is\napproved.\n\nRun `scripts\u002Fpr-state --summary \u003CPR>` once. Record the current-head check,\nreview, and PR-delivery fields described in\n`references\u002Freview-evidence.md`. For a cross-repository PR, use only the\nreported delivery fields as the push target; do not infer it from a local\n`fork` or `contributor` remote. Load that reference for exact-head review\nclassification, authentication fallbacks, and hidden-thread handling. Inspect\nmergeability separately through `references\u002Fmerge-conflicts.md`.\n\nIf the fresh mergeability query reports `mergeable=CONFLICTING` or\n`mergeStateStatus=DIRTY`, stop CI and review triage. This is an actionable PR\nblocker, not a clean or report-only terminal state. Load\n`references\u002Fmerge-conflicts.md`. If the user has explicitly authorized PR\nfixup or conflict resolution, resolve the conflict now (prefer a merge of the\nfresh base unless the user requests a rebase), verify the result, push it, and\nrestart this section with a new PR-state snapshot. If authorization is absent,\nreport the conflict and ask for it before mutating the branch. Do not triage\ncomments or checks against a conflicted head.\n\nFor pending CI, wait with `scripts\u002Fpr-await \u003CPR>`. It blocks below the\nconversation and prints one report when every check is terminal, so a wait of\nany length costs a single round-trip. Do not re-run `scripts\u002Fpr-state\n--summary` on a timer instead: each snapshot is a separate model turn that\nre-reads the whole context, and waiting is only about 6% of what such a turn\nactually does.\n\nDefault `--mode all-terminal` is the cost-correct choice and returns only when\nno check is pending, so every failure arrives in one report and is fixed in one\npass. It is also the correct choice for a reason unrelated to cost: a failed job\ncan be visible while its parent workflow is still running, so an early return\nreports a partial failure set. Use `--mode first-failure` only when the user\nwants the first failure interactively; it costs an extra full CI cycle per\nfailure. Pass `--deadline-min` for a user-stated limit; on exit 2 report the\nnamed pending checks as \"CI in progress.\"\n\nRead its exit code rather than re-deriving state: 0 clean, 1 terminal with\nfindings, 2 deadline with checks still pending, 3 blocked. Exit 3 covers every\ncase where a clean answer cannot be trusted: the PR merged or closed, a workflow\nneeds approval, access was lost, the merge-state query failed, the snapshot\nreported `errors` or a null unresolved-thread count, or the host toolchain\ncannot run `pr-state` correctly. Never downgrade an exit 3 to \"probably clean.\"\n\nExit 1 counts blocking reviews, not only threads: a current-head\n`CHANGES_REQUESTED` review can exist with no unresolved thread attached.\n\nEvery report records the jq and bash versions it ran under. That is provenance,\nnot a gate: `pr-state` used to fail silently on jq 1.6 and on the bash 3.2 that\nmacOS ships as `\u002Fbin\u002Fbash`, both of which made a dirty PR look clean, and both\nare fixed at the source. What guards against a degraded `pr-state` now is the\nsnapshot itself, which is stronger than any version check: a summary reporting\n`errors`, one whose unresolved-thread count is null, and one that does not parse\nare all treated as unknown rather than clean. A blocked report on an old\ntoolchain adds a note naming it as a possible cause. A push during the wait\nrestarts the gate against the new head and is reported.\n\nDo not use interactive `gh pr checks --watch` in the primary conversation: its\nTTY redraws make captured output unusable. Use the read-only `pr-poller` only\nwhen the user explicitly asked to wait or monitor and `pr-await` is unavailable.\nTreat a poller's unresolved\u002Fpending snapshot as provisional: it can predate a\nprimary-session push or thread resolution. Re-run `scripts\u002Fpr-state --summary\n\u003CPR>` at the current head before acting on it or declaring completion.\nIf a job remains pending beyond the workflow's configured timeout, or its status\nconflicts with the GitHub UI\u002FAPI, query the exact job with\n`gh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Factions\u002Fjobs\u002F\u003Cjob_id>` (or inspect the run with\n`gh run view \u003Crun_id>`) before calling CI hung or changing code. Treat the direct\nresult as current-head evidence only after its `head_sha` matches\n`checks_head_sha`; otherwise report the result as stale or unknown.\n\nFor a cross-repository PR whose current-head snapshot is unexpectedly sparse,\ninspect `approval_required_runs`. A current-head workflow with\n`conclusion=action_required` is blocked verification, not green or skipped CI.\nOnly after the user authorizes PR fixup, approve the exact run with\n`gh api --method POST repos\u002F\u003Cbase-owner>\u002F\u003Cbase-repo>\u002Factions\u002Fruns\u002F\u003Crun-id>\u002Fapprove`,\nthen re-run the summary and require jobs to materialize before polling. `gh run\napprove` is not a valid command.\n\nTreat the state as clean only when the current head has no failed or pending\nchecks, no merge conflict, no blocking review (an active `CHANGES_REQUESTED`\nor a review blocked at the exact current head), no unresolved review thread, no\nactionable issue comment, and qualifying exact-head semantic evidence where PR\ndelivery requires it.\n\n## 2. Fix CI Failures\n\nBefore changing code, confirm every reported failed check, its `run_id`, and\nthe parent workflow\u002Fjob status. A failed job can be visible while its workflow\nis still in progress; confirm its conclusion and failing step before treating\nit as reproducible code evidence. Use\n`scripts\u002Frun-quiet gh-run -- gh run view \u003Crun-id> --log-failed` so large logs do\nnot flood the conversation. If it returns only GitHub request\u002Ftransport lines\nor no failure text, treat logs as unavailable and, after terminal state, use\n`scripts\u002Fpr-state --job-log \u003Cjob_id>`. For temporary gaps or aggregate-only\nlogs, use the same fallback; it handles plain-text and ZIP responses and emits\nbounded context. Follow `references\u002Fci-troubleshooting.md`. Reproduce the exact\nfailed command where possible; CI-specific Go lint often needs\n`golangci-lint run .\u002F... --new-from-rev=\u003Cbase> --timeout=5m`.\n\nIf CI reports files or commits outside the PR diff, or a stale base SHA, resolve\nthe authoritative base repository, ref name, and current base SHA from PR\nmetadata. Fetch that ref from an explicit base remote, verify its tip matches\nthe reported SHA, and compare `git merge-base HEAD \u003Cbase-remote>\u002F\u003Cbase-ref>`\nwith `git diff \u003Cbase-remote>\u002F\u003Cbase-ref>...HEAD`; do not assume `origin\u002F\u003Cbase>`\nwhen `origin` points to a fork. Inspect the parent workflow\u002Frun to determine\nwhether a newer base commit caused the failure before changing product or docs\ncode. If the fix is already upstream, update or rebase the branch only when\nauthorized, rerun affected checks, and invalidate all prior exact-head evidence.\n\nFor unfamiliar, infrastructure, or E2E failures, load\n`references\u002Fci-troubleshooting.md` before changing code.\nAlso load it for unexpected zero-duration or no-op manual-review runs: event\nand workflow provenance can explain them without a product-code change.\n\nAn explicit request to run `pr fixup` owns every failed required check on the\ncurrent head. Never stop by calling a failure \"unrelated\" only because its\nfiles are outside the PR diff. Reproduce each leaf failure with retries\ndisabled, inspect its artifacts and shared fixtures\u002Fcleanup, and fix every\nvalid product, test, fixture, cleanup, or CI-contract defect it exposes. A\ndependent aggregate failure does not replace its leaf failures: trace the\naggregate to all failed jobs, fix the underlying failures, and wait for the\naggregate checks to rerun. If concrete evidence proves a failure is external\nafter this investigation, report the exact job\u002Flog\u002Freproduction evidence and\nkeep the PR blocked; do not call it ready while a required check is failed.\n\nFix with `\u002Ftdd` or `\u002Fe2e` as applicable, run focused checks, and keep each\nremediation scoped to the reported failure. Do not suppress a failure or mark a\ncheck clean without fresh evidence.\n\nIf a reproducible failure is outside the PR diff, compare the failing\nassertion with the current implementation and concurrent or sibling PRs before\nediting. If it is a stale test expectation, the smallest valid remediation may\nbe a test-only assertion update: keep it limited to the reported failure, run\nthe focused test, and call out that scope. Do not change unrelated production\nbehavior or duplicate a larger sibling change.\nWhen a remediation changes a documented behavior or contract, update the\nauthoritative spec\u002Fguidance, plan, and task file when present; commit docs and\ncode together, keep regression tests and verification commands aligned, and\nre-check the documentation before completion. Record why no update is needed\nwhen the behavior remains internal.\n\n## 3. Triage And Address Reviews\n\nUse `scripts\u002Fpr-resolve list \u003CPR>` to obtain unresolved threads. Its previews\ncan be truncated, so expand every listed review thread with\n`scripts\u002Fpr-resolve show \u003CPR> \u003Cthread_id>` before deciding how to handle it.\nUse `scripts\u002Fpr-state --comment \u003Ccomment_id>` only for a flat comment view when\na thread context is not available. Validate against the current head, the spec,\nand existing architecture before editing or replying.\n\nEvery unresolved thread requires an explicit disposition, regardless of its\nauthor, bot identity, visibility, or apparent severity. Record exactly one of\nthese dispositions:\n\n- `actionable`: make the valid code or test change, verify it, cite the\n  resulting commit in the reply, and resolve the thread when writes are\n  authorized.\n- `already addressed`: verify the current implementation or an existing commit,\n  explain where it is addressed, and resolve the thread when writes are\n  authorized.\n- `informational` or `optional`: make no code change, acknowledge the information\n  or suggestion in a reply, and resolve it when complete cleanup is requested.\n- `invalid`: do not make an invalid code change or silently ignore the finding;\n  reply with concrete reasoning grounded in the code, spec, or architecture,\n  then resolve it only after that pushback is posted and writes are authorized.\n\nA classification is not a disposition. A thread is not complete merely because\nit was called optional, informational, already addressed, or invalid. GitHub\nreplies and thread resolution are external writes. A request such as \"complete\ncleanup\", \"clean up all review threads\", or \"leave no threads unresolved\"\nexplicitly authorizes a concise reply and resolution for every unresolved\nthread, including informational, optional, and invalid findings. A request to\naddress selected comments authorizes replies and resolution only for those\nselected threads. A review-only request authorizes no writes. When writes are\nnot authorized, record every disposition, report the still-unresolved thread,\nand do not declare the PR clean.\n\nFor code changes, push the fix and pass targeted verification before replying\nand resolving. For non-code dispositions, verify the current head first, then\nuse the atomic helper path\n`scripts\u002Fpr-resolve reply \u003CPR> \u003Ccomment_id> \u003Cthread_id> --body-file \u003Cpath>` to\nreply, resolve, and react in one operation when the body contains Markdown or\nshell metacharacters. For short plain-text bodies, a safely quoted argument is\nacceptable. Never interpolate review text into an unquoted shell command or\nuse backticks in the command itself. After the helper returns, re-fetch the\nthread and verify the posted reply body and resolved state before treating the\ndisposition as complete.\nThen rerun\n`scripts\u002Fpr-resolve list \u003CPR>` and the exact-head `scripts\u002Fpr-state --summary\n\u003CPR>` check before reporting.\n\nFor an ordering or concurrency finding, trace the complete producer → event-bus\ntransport → gateway\u002Fclient path. Sequential publishes do not prove delivery\norder when a remote bus uses separate subscriptions; consolidate one stream or\nadd sequence-aware buffering when order is contractual, and cover both the\ntransport boundary and local emulator.\n\nWhen feedback says an action must remain reachable, add and run a regression at\nthe legal minimum width. Verify the actual hit target (for example,\n`elementFromPoint()` at the control center) and clickability, not only\n`toBeVisible`, before pushing.\n\n## 4. Commit, Verify, Push\n\nCommit through `\u002Fcommit`, then rerun only the unit, integration, or E2E command\naffected by the remediation. Push when that targeted check passes for the exact\ncurrent `HEAD`. For a cross-repository PR, push the exact current `HEAD` to the\nsummary's authoritative head repository and ref only when\n`pr.maintainer_can_modify` is true. Re-fetch the PR afterward and require its\n`pr.head_ref_oid` to equal local `HEAD`; an upstream remote comparison is not\nsufficient. Run broad `\u002Fverify` only if the user explicitly requests it or the\nPR\u002FCI finding requires it.\nAfter every push, also run a fresh\n`gh pr view \u003CPR> --json baseRefName,headRefOid,mergeable,mergeStateStatus` (or\nequivalent) at that pushed head. Require `headRefOid` to equal local `HEAD` and\nconfirm `mergeable` is not `CONFLICTING` and `mergeStateStatus` is not `DIRTY`;\n`scripts\u002Fpr-state --summary` does not include mergeability.\n\nImmediately before a remediation commit or push—and again after long-running\nremediation—refresh PR state. Require the PR to remain open and its head ref to\nmatch the local branch. Before a push, compare the remote head OID with the\nlocal upstream tip; after the push, require the PR head OID to equal local\n`HEAD`. If the PR merged or closed, do not recreate its deleted branch with a\nstale push: preserve the local fix and ask before creating a clean follow-up.\n\nAfter any rebase or force-push, fetch the PR base and compare local `HEAD`, the upstream tip, and `pr.head_ref_oid`; rerun affected checks.\nA rebase onto a newer base invalidates prior evidence: rerun the exact failed\ncommand and any package-level gate required by whole-file rules (for example\nmax-lines). Then rerun `scripts\u002Fpr-resolve list \u003CPR>` and `scripts\u002Fpr-state --summary \u003CPR>`; distinguish stale\u002Fcurrent\nfailures and report pending checks separately. Use `--force-with-lease`, never an unconditional force-push.\nIf the rebase or conflict resolution touched `AGENTS.md`, `CLAUDE.md`, or a\nskill\u002Freference file, run the shared harness validation in\n`.agents\u002Fskills\u002Fharness-improvement\u002Freferences\u002Fvalidation.md` before pushing.\n\n## 5. Re-check\n\nAfter every push, re-fetch current-head state and run\n`scripts\u002Fpr-resolve list \u003CPR>` (and `show` for any thread you may answer), then\n`scripts\u002Fpr-state --summary \u003CPR>` again for the new head. For explicit\nconsolidation, verify the target head before commenting\u002Fclosing the superseded\nPR; preserve its branch unless deletion is requested. Automated reviewers may\nresolve or replace threads; do not reply to or resolve a thread that fresh state\nreports as resolved. Before replying to a pre-push thread, run\n`scripts\u002Fpr-resolve show \u003CPR> \u003Cthread_id>`; if it reports `resolved: true` (often\nwith an `Addressed in commit ...` marker), record the thread as auto-resolved and\ndo not post a duplicate reply. Continue replying\u002Fresolving only for `resolved: false` threads, including hidden unresolved threads.\nTreat each fresh summary as a new review-evidence snapshot: inspect every\nnon-empty body in `review_evidence.exact_current_head_reviews[]`, even when\n`unresolved_review_thread_count=0` and `scripts\u002Fpr-resolve list` is empty.\nClassify current-head review bodies and top-level bot\u002Fissue comments before\ndeclaring the PR clean; empty thread and issue-comment counts are insufficient.\nTreat a non-empty `hidden_unresolved_threads` value in that fresh snapshot as a\nmandatory hidden-thread gate: expand and disposition each hidden thread, then\nrun `scripts\u002Fpr-resolve list \u003CPR>` again after the refresh and immediately\nbefore reporting.\nRequire `checks_head_sha` to match that head, report pending checks separately\nfrom failures, and rerun `scripts\u002Fpr-resolve list \u003CPR>` before declaring the\nPR clean. The final predicate must also require\n`hidden_unresolved_threads=[]`; do not require filtered and unresolved counts to\nbe equal because the filtered count includes resolved threads. Treat prior review\nevidence as stale. When the user authorized thread writes, every unresolved\nthread still needs an explicit reply and resolution matching its disposition.\nA duplicate or stale bot thread needs the same treatment once current source\nproves the finding is already fixed, including a thread surfaced only in\n`hidden_unresolved_threads`; only current-head actionable threads drive code\nchanges. Declare the PR clean only when the\nexact-current-head review classification reports no unaddressed findings,\n`checks_snapshot_complete=true`, `failed_checks=[]`, `pending_checks=[]`,\n`approval_required_runs=[]`, `actionable_issue_comment_count=0`,\n`unresolved_review_thread_count=0`, `hidden_unresolved_threads=[]`, there is no\nmerge conflict, and\n`scripts\u002Fpr-resolve list \u003CPR>` is empty. Within\nthe user's monitoring limit, continue checking after resolutions until automated\nreview jobs are terminal; otherwise report the exact pending check names.\n\nIf the user explicitly requested a persistent Kandev plan update and the task\nhas an external Kandev plan, call `get_task_plan_kandev` before fixup and\n`update_task_plan_kandev` after fixup with the remediation commit, final\nexact-head check counts, resolved-thread state, and mergeability. Without that\nauthorization, report the plan update as pending and do not invoke Kandev task\nor session APIs. Batch plan\u002Ftask synchronization into the final documentation\ncommit. Record the prior head's fixup evidence before a plan commit\u002Fpush: that\npush restarts CI and invalidates the snapshot. For tracked `docs\u002Fplans\u002F**`\nartifacts, keep prose head-agnostic and record remediation scope\u002Flocal\nverification before that commit; then rerun `scripts\u002Fpr-state --summary` and\n`scripts\u002Fpr-resolve list` for the new head and report its pending checks\nseparately. Mark prior current-head claims historical\u002Fsuperseded when a new\nhead replaces them; report only the latest head's SHA, CI\u002Freview counts, and\nmergeability. Do not leave planned verification marked unstarted after it has run.\n\nBefore declaring fixup complete, verify `git status --short` is clean,\n`git rev-parse HEAD` equals `git rev-parse @{upstream}`, the PR head equals\nlocal `HEAD`, and the fresh mergeability state is not conflicting. Do not call\nthe PR clean from CI\u002Freview counts alone when the worktree or remote tip still\ndiffers.\n\nThe phrase \"ready to merge\" is reserved for a fresh current-head snapshot\nwith every required check successful or explicitly skipped, no pending or\nfailed leaf or aggregate check, no unresolved review thread, no merge conflict,\nand the local, upstream, and PR head OIDs aligned. A clean local reproduction\ndoes not waive a failed remote check; push the remediation and re-check the\nnew head first.\n\n## 6. User-Requested Merge\n\nMerge only after the user explicitly asks and the current-head state is clean.\nFrom a linked worktree, run `gh pr merge \u003CPR> --squash` without\n`--delete-branch`: that flag can attempt a local checkout of the base branch\nand fail when another worktree owns it, even after the remote merge succeeds.\nReport the remote merge separately. Delete a remote or local branch only when\nrequested and through a worktree-safe cleanup flow.\n\n## Guardrails\n\n- Do not create Kandev subtasks unless the user explicitly asks for task\n  tracking.\n- Do not use native delegation or a full-history context fork to poll CI.\n- Do not push, post comments, or resolve threads when the user asked for review\n  only.\n- Do not silently dismiss an invalid finding; every invalid thread needs a\n  concrete pushback disposition, and an authorized complete cleanup must post\n  that explanation before resolving it.\n- Do not proceed with an unverified PR when mandatory verification is blocked.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fpr-fixup",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill pr-fixup",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill pr-fixup",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill pr-fixup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fpr-fixup\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fci-troubleshooting.md","REFERENCE","参考文档",11707,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fpr-fixup\u002Freferences\u002Fci-troubleshooting.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fmerge-conflicts.md",7212,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fpr-fixup\u002Freferences\u002Fmerge-conflicts.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Freview-evidence.md",7789,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fpr-fixup\u002Freferences\u002Freview-evidence.md",[61,68,73,80,87,94],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":69,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]