[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79X2G7DM5NJMRAEYMM3G85S":3,"skill-same:01M79X2G7DM5NJMRAEYMM3G85S":61},{"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":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79X2G7DM5NJMRAEYMM3G85S","triage",null,"Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.","Blind-Striker\u002Fagent-skills-and-plugins","Blind-Striker","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1965259?v=4","01M79WFXTE5PH0C1VB7B54ANMN","Deniz İrgin","01M79WFXV5KZ5GST1K8G035DM5",1,"MIT","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fcodex\u002Fdeniz-process\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: triage\ndescription: Move issues and external PRs through a state machine of triage\n  roles, categorise, verify, grill if needed, and write agent-ready briefs.\n---\n\n# Triage\n\nMove issues on the project issue tracker through a small state machine of triage roles.\n\nIf this repo treats external pull requests as a request surface (see the issue-tracker config), triage covers them too: **a PR is an issue with attached code**, using the same roles, same states, and same machine, with a few deltas marked \"for a PR\" below. Resolve a bare `#42` to an issue or PR per the tracker config.\n\nEvery comment or issue posted to the issue tracker during triage **must** start with this disclaimer:\n\n```\n> *This was generated by AI during triage.*\n```\n\n## Reference docs\n\n- [AGENT-BRIEF.md](AGENT-BRIEF.md): how to write durable agent briefs\n- [OUT-OF-SCOPE.md](OUT-OF-SCOPE.md): how the `.out-of-scope\u002F` knowledge base works\n\n## Roles\n\nTwo **category** roles:\n\n- `bug`: something is broken\n- `enhancement`: new feature or improvement\n\nFive **state** roles:\n\n- `needs-triage`: maintainer needs to evaluate\n- `needs-info`: waiting on reporter for more information\n- `ready-for-agent`: fully specified, ready for an AFK agent\n- `ready-for-human`: needs human implementation\n- `wontfix`: will not be actioned\n\nFor a PR, the same states read against the attached code: `ready-for-agent` means a brief is attached and an agent should take the next step on the diff; `ready-for-human` means it's ready for a human to merge.\n\nEvery triaged issue should carry exactly one category role and one state role. If state roles conflict, flag it and ask the maintainer before doing anything else.\n\nThese are canonical role names. The actual label strings used in the issue tracker may differ. The mapping should have been provided to you. If not, tell the user to run `$deniz-process:setup-matt-pocock-skills`.\n\nState transitions: an unlabeled issue normally goes to `needs-triage` first; from there it moves to `needs-info`, `ready-for-agent`, `ready-for-human`, or `wontfix`. `needs-info` returns to `needs-triage` once the reporter replies. The maintainer can override at any time; flag transitions that look unusual and ask before proceeding.\n\n## Invocation\n\nThe maintainer invokes this triage skill and describes what they want in natural language. Interpret the request and act. Examples:\n\n- \"Show me anything that needs my attention\"\n- \"Let's look at #42\" (issue or PR)\n- \"Move #42 to ready-for-agent\"\n- \"What's ready for agents to pick up?\"\n\n## Show what needs attention\n\nQuery the issue tracker and present three buckets, oldest first:\n\n1. **Unlabeled**: never triaged.\n2. **`needs-triage`**: evaluation in progress.\n3. **`needs-info` with reporter activity since the last triage notes**: needs re-evaluation.\n\nWhen PRs are in scope, include external PRs in these buckets and tag each line `[PR]` or `[issue]`. Discovery surfaces only *external* PRs (the tracker config defines who counts as external), so a collaborator's in-flight PR is not triage work. This filter is discovery-only; an explicitly named PR is always triaged regardless of author.\n\nShow counts and a one-line summary per item. Let the maintainer pick.\n\n## Triage a specific issue or PR\n\n1. **Gather context.** Read the full issue or PR (body, comments, labels, author, dates; for a PR, the diff too). Parse any prior triage notes so you don't re-ask resolved questions. Explore the codebase using the project's domain glossary, respecting ADRs in the area. Run two checks against the codebase: (a) **redundancy**: search for an existing implementation of the requested behavior by domain concept (not just the request's wording), and report where you looked. If found, it's an already-implemented `wontfix` (step 5). (b) **prior rejection**: read `.out-of-scope\u002F*.md` and surface any that resembles this request.\n\n2. **Recommend.** Tell the maintainer your category and state recommendation with reasoning, plus a brief codebase summary relevant to the request (including whether it's already implemented). Wait for direction.\n\n3. **Verify the claim.** Before any grilling, check that the claim holds up. For a bug, reproduce it from the reporter's steps. For a PR, confirm the diff does what it claims: check it out, run the relevant tests or commands. Report what happened: confirmed (with code path), failed, or insufficient detail (a strong `needs-info` signal). A confirmed verification makes a much stronger agent brief.\n\n4. **Grill (if needed).** If the request needs fleshing out, invoke `$deniz-process:grilling` and `$deniz-process:domain-modeling`, and grill it into shape a round of questions at a time, sharpening domain terms and updating `GLOSSARY.md`\u002FADRs inline as decisions land.\n\n5. **Apply the outcome:**\n   - `ready-for-agent`: post an agent brief comment ([AGENT-BRIEF.md](AGENT-BRIEF.md)).\n   - `ready-for-human`: same structure as an agent brief, but note why it can't be delegated (judgment calls, external access, design decisions, manual testing).\n   - `needs-info`: post triage notes (template below).\n   - For `wontfix`, close the issue, with the comment depending on *why*:\n     - **Already implemented**: the change already exists in the codebase. Point to where it lives; do **not** write to `.out-of-scope\u002F` (that KB is for *rejected* requests, not built ones).\n     - **Rejected (bug)**: give a polite explanation, then close.\n     - **Rejected (enhancement)**: write to `.out-of-scope\u002F`, link to it from a comment, then close ([OUT-OF-SCOPE.md](OUT-OF-SCOPE.md)).\n   - `needs-triage`: apply the role. Optional comment if there's partial progress.\n\n## Quick state override\n\nIf the maintainer says \"move #42 to ready-for-agent\", trust them and apply the role directly. State what you are about to do (role changes, comment, close), then do it in the same turn. Skip grilling. If moving to `ready-for-agent` without a grilling session, ask whether they want to write an agent brief.\n\n## Needs-info template\n\n```markdown\n## Triage Notes\n\n**What we've established so far:**\n\n- point 1\n- point 2\n\n**What we still need from you (@reporter):**\n\n- question 1\n- question 2\n```\n\nCapture everything resolved during grilling under \"established so far\" so the work isn't lost. Questions must be specific and actionable, not \"please provide more info\".\n\n## Resuming a previous session\n\nIf prior triage notes exist on the issue or PR, read them, check whether the reporter has answered any outstanding questions, and present an updated picture before continuing. Don't re-ask resolved questions.\n","# Triage\n\nMove issues on the project issue tracker through a small state machine of triage roles.\n\nIf this repo treats external pull requests as a request surface (see the issue-tracker config), triage covers them too: **a PR is an issue with attached code**, using the same roles, same states, and same machine, with a few deltas marked \"for a PR\" below. Resolve a bare `#42` to an issue or PR per the tracker config.\n\nEvery comment or issue posted to the issue tracker during triage **must** start with this disclaimer:\n\n```\n> *This was generated by AI during triage.*\n```\n\n## Reference docs\n\n- [AGENT-BRIEF.md](AGENT-BRIEF.md): how to write durable agent briefs\n- [OUT-OF-SCOPE.md](OUT-OF-SCOPE.md): how the `.out-of-scope\u002F` knowledge base works\n\n## Roles\n\nTwo **category** roles:\n\n- `bug`: something is broken\n- `enhancement`: new feature or improvement\n\nFive **state** roles:\n\n- `needs-triage`: maintainer needs to evaluate\n- `needs-info`: waiting on reporter for more information\n- `ready-for-agent`: fully specified, ready for an AFK agent\n- `ready-for-human`: needs human implementation\n- `wontfix`: will not be actioned\n\nFor a PR, the same states read against the attached code: `ready-for-agent` means a brief is attached and an agent should take the next step on the diff; `ready-for-human` means it's ready for a human to merge.\n\nEvery triaged issue should carry exactly one category role and one state role. If state roles conflict, flag it and ask the maintainer before doing anything else.\n\nThese are canonical role names. The actual label strings used in the issue tracker may differ. The mapping should have been provided to you. If not, tell the user to run `$deniz-process:setup-matt-pocock-skills`.\n\nState transitions: an unlabeled issue normally goes to `needs-triage` first; from there it moves to `needs-info`, `ready-for-agent`, `ready-for-human`, or `wontfix`. `needs-info` returns to `needs-triage` once the reporter replies. The maintainer can override at any time; flag transitions that look unusual and ask before proceeding.\n\n## Invocation\n\nThe maintainer invokes this triage skill and describes what they want in natural language. Interpret the request and act. Examples:\n\n- \"Show me anything that needs my attention\"\n- \"Let's look at #42\" (issue or PR)\n- \"Move #42 to ready-for-agent\"\n- \"What's ready for agents to pick up?\"\n\n## Show what needs attention\n\nQuery the issue tracker and present three buckets, oldest first:\n\n1. **Unlabeled**: never triaged.\n2. **`needs-triage`**: evaluation in progress.\n3. **`needs-info` with reporter activity since the last triage notes**: needs re-evaluation.\n\nWhen PRs are in scope, include external PRs in these buckets and tag each line `[PR]` or `[issue]`. Discovery surfaces only *external* PRs (the tracker config defines who counts as external), so a collaborator's in-flight PR is not triage work. This filter is discovery-only; an explicitly named PR is always triaged regardless of author.\n\nShow counts and a one-line summary per item. Let the maintainer pick.\n\n## Triage a specific issue or PR\n\n1. **Gather context.** Read the full issue or PR (body, comments, labels, author, dates; for a PR, the diff too). Parse any prior triage notes so you don't re-ask resolved questions. Explore the codebase using the project's domain glossary, respecting ADRs in the area. Run two checks against the codebase: (a) **redundancy**: search for an existing implementation of the requested behavior by domain concept (not just the request's wording), and report where you looked. If found, it's an already-implemented `wontfix` (step 5). (b) **prior rejection**: read `.out-of-scope\u002F*.md` and surface any that resembles this request.\n\n2. **Recommend.** Tell the maintainer your category and state recommendation with reasoning, plus a brief codebase summary relevant to the request (including whether it's already implemented). Wait for direction.\n\n3. **Verify the claim.** Before any grilling, check that the claim holds up. For a bug, reproduce it from the reporter's steps. For a PR, confirm the diff does what it claims: check it out, run the relevant tests or commands. Report what happened: confirmed (with code path), failed, or insufficient detail (a strong `needs-info` signal). A confirmed verification makes a much stronger agent brief.\n\n4. **Grill (if needed).** If the request needs fleshing out, invoke `$deniz-process:grilling` and `$deniz-process:domain-modeling`, and grill it into shape a round of questions at a time, sharpening domain terms and updating `GLOSSARY.md`\u002FADRs inline as decisions land.\n\n5. **Apply the outcome:**\n   - `ready-for-agent`: post an agent brief comment ([AGENT-BRIEF.md](AGENT-BRIEF.md)).\n   - `ready-for-human`: same structure as an agent brief, but note why it can't be delegated (judgment calls, external access, design decisions, manual testing).\n   - `needs-info`: post triage notes (template below).\n   - For `wontfix`, close the issue, with the comment depending on *why*:\n     - **Already implemented**: the change already exists in the codebase. Point to where it lives; do **not** write to `.out-of-scope\u002F` (that KB is for *rejected* requests, not built ones).\n     - **Rejected (bug)**: give a polite explanation, then close.\n     - **Rejected (enhancement)**: write to `.out-of-scope\u002F`, link to it from a comment, then close ([OUT-OF-SCOPE.md](OUT-OF-SCOPE.md)).\n   - `needs-triage`: apply the role. Optional comment if there's partial progress.\n\n## Quick state override\n\nIf the maintainer says \"move #42 to ready-for-agent\", trust them and apply the role directly. State what you are about to do (role changes, comment, close), then do it in the same turn. Skip grilling. If moving to `ready-for-agent` without a grilling session, ask whether they want to write an agent brief.\n\n## Needs-info template\n\n```markdown\n## Triage Notes\n\n**What we've established so far:**\n\n- point 1\n- point 2\n\n**What we still need from you (@reporter):**\n\n- question 1\n- question 2\n```\n\nCapture everything resolved during grilling under \"established so far\" so the work isn't lost. Questions must be specific and actionable, not \"please provide more info\".\n\n## Resuming a previous session\n\nIf prior triage notes exist on the issue or PR, read them, check whether the reporter has answered any outstanding questions, and present an updated picture before continuing. Don't re-ask resolved questions.\n",{"name":5,"description":7},"master","b30b1c1908dbc56a8184128f18803053d762ccb5","codex\u002Fdeniz-process\u002Fskills\u002Ftriage",0,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins","https:\u002F\u002Fgithub.com\u002FBlind-Striker","denizirgin.com","VP of Engineering - \r\n@armutcom @homeruntech @prontopro\r\n |  Speaker \r\n@CodeFiction\r\n, http:\u002F\u002Fcodefiction.tech | Developer, gamer, blogger, maiden iron fan","2026-11-13 00:23:18",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill triage",{"tool":39,"command":40},"bunx","bunx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill triage",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fcodex\u002Fdeniz-process\u002Fskills\u002Ftriage\u002FSKILL.md",true,[47,53,57],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"AGENT-BRIEF.md","REFERENCE","参考文档",7952,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fcodex\u002Fdeniz-process\u002Fskills\u002Ftriage\u002FAGENT-BRIEF.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"agents\u002Fopenai.yaml",229,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fcodex\u002Fdeniz-process\u002Fskills\u002Ftriage\u002Fagents\u002Fopenai.yaml",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"OUT-OF-SCOPE.md",4667,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fcodex\u002Fdeniz-process\u002Fskills\u002Ftriage\u002FOUT-OF-SCOPE.md",[62,69,76,83,90,97],{"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},"01M79YGWBJ52PHMSTKJ3RJ3AWR","writing-tunit-tests","Write tests in TUnit — the attributes, the async assertion model, data-driven cases, lifecycle hooks, and the parallelism rules. USE FOR writing or fixing a test in a TUnit project, translating a test idea into TUnit syntax, or reviewing TUnit test code for API mistakes. DO NOT USE FOR deciding what to test, judging whether a test is any good, or running tests.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fwriting-tunit-tests\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79YGR3Y9RCRS6TD71D0KKP8","dotnet-walls","Walls for a .NET change in a repository without its own quality gates — pinned, ephemeral analyzer, format, clone and scanner commands for the verify step, their identity ratchet, and the build traps. Use during a walls preflight, or when a worker's verify step needs .NET quality gates.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fdotnet-walls\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M79YGFNJBST7D803NQW3SBYM","csharp-15","Write, review and modernize C# 15 (.NET 11) code correctly. Covers every C# 15 feature - collection expression arguments (`[with(...), ...]`), union types (`union`, `[Union]`, `IUnion`, custom unions), closed class hierarchies (`closed`), extension indexers, labeled `break`\u002F`continue`, non-virtual static interface members on runtimes without default interface methods, and the preview memory-safety model (`unsafe(expr)`, `safe`, requires-unsafe members). Use when code targets net11.0 or LangVersion 15\u002Fpreview, when the user mentions any of these features, when replacing marker interfaces, OneOf-style results, `goto`\u002Fflag loop exits or capacity\u002Fcomparer boilerplate, or when the build reports CS8121, CS8509, CS8655, CS8510, CS0121\u002FCS0411 on a `with(...)` element, CS9370, CS9380 or CS9363.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fcsharp-15\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M79YGAV031473HSX6FN87ENH","verified-waves","Run one task as verified multi-agent waves. Plans the fan-out, sends findings to fresh skeptics, keeps a ledger, and reports N of M done; small tasks stay solo.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fverified-waves\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M79YG6QXNND4WRPP3GATSY8J","harness","The bundled dispatch harness, which runs a task file on worker models through OpenCode or Codex, fences their writes, escalates their asks to the operator, settles each result from git and its verify commands, and records every step in a ledger. Its commands, task file, modes and write fence, configuration, runs and their recovery, ledger and exit codes.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fharness\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M79YG2P5S91SDTA5912XJ4FV","delegating-to-worker-models","Use when you hand off implementation, a plan, research a decision will rely on, or a review, and you brief the worker and check what comes back. A subagent that searches, reads in parallel, or keeps your context small is ordinary tool use. Covers what stays with you, the mechanism, assigning work by strength, the walls preflight, prompts without contradictions, the worker contract and model profiles, evidence from your own run, review, and the fix-up loop.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fdelegating-to-worker-models\u002FSKILL.md",[],[]]