[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4RN7REXARMQ18V8WZB29H":3,"skill-same:01M7F4RN7REXARMQ18V8WZB29H":55},{"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":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":44},"01M7F4RN7REXARMQ18V8WZB29H","to-tickets",null,"Break a specification into independently mergeable tickets, publish them in their responsible repositories with native parent and blocking links, and return the split for independent review.","lutzseverino\u002Fpostern","lutzseverino","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28309837?v=4","01M77NN0YKH0YYGY7W7ER23MX0","Jasper","01M7F4MESFQZ45SVN7DQD7Y8D4",0,"MIT","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: to-tickets\ndescription: Break a specification into independently mergeable tickets, publish them in their responsible repositories with native parent and blocking links, and return the split for independent review.\ndisable-model-invocation: true\n---\n\nA prompt or brief naming this skill is its invocation.\n\n# To Tickets\n\nBreak a plan, spec, or conversation into a set of **tickets**: tracer-bullet vertical slices, each declaring the tickets that **block** it.\n\nThe issue tracker and triage label vocabulary should have been provided to you.\n\n## Process\n\n### 1. Gather context\n\nWork from whatever is already in the conversation context. If the user passes a reference (a spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.\n\nFor a grill, consume the single specification published by `to-spec`; if it\ndoes not exist yet, invoke `to-spec` first. Keep that specification as the\nparent across repositories. Copy relied-on decisions with their dates and\nquoted words into every ticket contract, so private records are unnecessary.\nFor an amendment, first apply the contribution guide's Triage amendment rule\nand consume the revised specification; work only the delta, revising affected\ncontracts and native relationships.\n\n### 2. Explore the codebase (optional)\n\nIf you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.\n\nLook for opportunities to prefactor the code to make the implementation easier. \"Make the change easy, then make the easy change.\"\n\n### 3. Draft vertical slices\n\nBreak the work into **tracer bullet** tickets.\n\n\u003Cvertical-slice-rules>\n\n- Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests): vertical, NOT a horizontal slice of one layer\n- A completed slice is demoable or verifiable on its own\n- Each slice is sized to fit in a single fresh context window\n- Any prefactoring should be done first\n\n\u003C\u002Fvertical-slice-rules>\n\nGive each ticket its **blocking edges**: the other tickets that must complete\nbefore it can start. Keep dependencies cycle-free. A ticket with no blockers\nuses the contribution guide's Readiness and installed parent-readiness rules.\n\n**Wide refactors are the exception to vertical slicing.** A **wide refactor** is one mechanical change (rename a column, retype a shared symbol) whose **blast radius** fans across the whole codebase, so a single edit breaks thousands of call sites at once and no vertical slice can land green. Don't force it into a tracer bullet; sequence it as **expand–contract**. First expand: add the new form beside the old so nothing breaks. Then migrate the call sites over in batches sized by blast radius (per package, per directory), each batch its own ticket blocked by the expand, keeping CI green batch to batch because the old form still exists. Finally contract: delete the old form once no caller remains, in a ticket blocked by every migrate batch. Every ticket's change merges into its base branch on its own, with its checks passing: when even the batches can't stay green alone, fold the batches that can't into one ticket.\n\n**Live acceptance is a ticket of its own.** When work must be shown on a live system, split it into a **source ticket**, which closes when its pull request merges, and a **live-acceptance ticket**, blocked by the source ticket, whose acceptance criteria are the recorded evidence that the deployed change behaves on the live system as its contract says. A merge never closes it: the source ticket's pull request links it without a closing reference, and it closes only once that evidence is recorded on it. Its live steps take the route the installed rules give work that needs host access.\n\n### 4. Prepare the split for independent review\n\nPresent the proposed breakdown as a numbered list. For each ticket, show:\n\n- **Title**: short descriptive name\n- **Blocked by**: which other tickets (if any) must complete first\n- **What it delivers**: the end-to-end behaviour this ticket makes work\n\nAttach evidence for granularity, real dependencies, independently mergeable\nslices and test seams, and identify any factual verification the independent\nreviewer must finish. Reuse recorded answers and plan approval. Read and apply\nthe contribution guide's Triage inference test, inferred-list and\nowner-question rules to unanswered choices.\n\nReturn the proposed split and evidence for the orchestrating agent's decision\nand independent acceptance under the guide's Triage rules. Use its correction\nand fact-finding routes for feedback rather than an owner breakdown quiz.\n\n### 5. Publish the tickets to the configured tracker\n\nPublish the proposed tickets awaiting review. **How** depends on the configured\ntracker; the tickets are the same either way, only the shape of the blocking\nedges changes:\n\n- **Local files** → write one file per ticket under `.scratch\u002F\u003Cfeature-slug>\u002Fissues\u002F\u003CNN>-\u003Cslug>.md`, numbered from `01` in dependency order (blockers first). Each file's \"Blocked by\" lists the numbers\u002Ftitles it depends on. Use the per-ticket file template below: one ticket per file, never a single combined file.\n- **A real issue tracker (GitHub, Linear, …)** → publish one issue per ticket in its responsible repository, in dependency order (blockers first) so each ticket's blocking edges can reference real identifiers. Link each ticket to the one specification parent and its blockers with the platform's native sub-issue and blocking relationships: the \"Parent\" and \"Blocked by\" sections restate those links for the reader and never stand in for them. If a native link can't be created, stop publication progression and report the exact missing parent\u002Fblocker relationship and platform failure. A text-only edge is never reported as established. Before publishing, read `.repo-standards\u002Frules\u002Fcomments.md#disclaimers`.\n\nUse the guide's direct-body-contract publication route. Return the proposed\nsplit, exact published contracts and established native links to the\norchestrating agent for acceptance under the guide's Triage and Readiness\nsections and the installed parent-readiness rules, including after amendments.\n\nOnce reviewed, work the **frontier**: any ready ticket whose blockers are all done. For a purely linear chain that means top to bottom.\n\nOnce a ticket is ready, nobody edits it to record progress, ticking its acceptance criteria included: progress lives in linked pull requests, sub-issue states and comments. A ticket closes when its own acceptance criteria hold.\n\nKeep the parent open. Modify its contract only for an authorized amendment;\npublication progress belongs in comments and native sub-issue states.\n\n\u003Clocal-ticket-template>\n\n# \u003CNN>: \u003CTicket title>\n\n**What to build:** the end-to-end behaviour this ticket makes work, from the user's perspective, not a layer-by-layer implementation list.\n\n**Blocked by:** the numbers\u002Ftitles of the tickets that gate this one, or \"None (readiness still required)\".\n\n**Status:** state:triage\n\n- [ ] Acceptance criterion 1\n- [ ] Acceptance criterion 2\n\n\u003C\u002Flocal-ticket-template>\n\n\u003Cissue-template>\n\n## Parent\n\nA reference to the parent issue on the tracker (if the source was an existing issue, otherwise omit this section).\n\n## What to build\n\nThe end-to-end behaviour this ticket makes work, from the user's perspective, not layer-by-layer implementation.\n\n## Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n\n## Blocked by\n\n- A reference to each blocking ticket, or \"None (readiness still required)\".\n\n\u003C\u002Fissue-template>\n\nIn either form, avoid specific file paths or code snippets: they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it and note briefly that it came from a prototype. Trim to the decision-rich parts, not a working demo, just the important bits.\n\n## Reads\n\nPaths are relative to the repository root.\n\n- `docs\u002Fagents\u002Fissue-tracker.md` and `docs\u002Fagents\u002Ftriage-labels.md`: the\n  configured tracker and its triage label vocabulary. When the tracker config\n  is missing and no tracker was provided, ask the user whether to publish to\n  local files or a real tracker; when the label config is missing, use the\n  canonical role names as the label strings.\n- `.repo-standards\u002Frules\u002Fcomments.md`: the installed comment rules, whose\n  section the posting steps name. When it is missing, post issue bodies and\n  comments as the steps describe.\n- `GLOSSARY.md` and the ADRs in `docs\u002Fadr\u002F`: the domain vocabulary and\n  decisions to respect. When either is missing, use the codebase's own words.\n- The installed rules, such as the `github-repository-configuration` rules,\n  which the `repository-standards` skill looks up: the companion labels\n  readiness needs, and the route for work that needs host access. When they\n  are missing, readiness carries no companion labels, and a live-acceptance\n  ticket takes no route of its own.\n- `.scratch\u002F`: the local-files tracker's tickets. When it is missing, create\n  it as step 5 says.\n- `CONTRIBUTING.md`: inference, split authority, amendments and readiness. If\n  missing, use `grilling`'s missing-guide fallback and independent exact-revision review, and\n  ask the user only for unresolved owner choices.\n- The `grilling` skill: the inference fallback, only when the contribution\n  guide is missing. If also missing, report it and stop for the missing policy.\n- The `to-spec` skill: publish the single specification before a grill's\n  tickets. If missing, report it and stop ticket publication until a\n  specification exists.\n","A prompt or brief naming this skill is its invocation.\n\n# To Tickets\n\nBreak a plan, spec, or conversation into a set of **tickets**: tracer-bullet vertical slices, each declaring the tickets that **block** it.\n\nThe issue tracker and triage label vocabulary should have been provided to you.\n\n## Process\n\n### 1. Gather context\n\nWork from whatever is already in the conversation context. If the user passes a reference (a spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.\n\nFor a grill, consume the single specification published by `to-spec`; if it\ndoes not exist yet, invoke `to-spec` first. Keep that specification as the\nparent across repositories. Copy relied-on decisions with their dates and\nquoted words into every ticket contract, so private records are unnecessary.\nFor an amendment, first apply the contribution guide's Triage amendment rule\nand consume the revised specification; work only the delta, revising affected\ncontracts and native relationships.\n\n### 2. Explore the codebase (optional)\n\nIf you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.\n\nLook for opportunities to prefactor the code to make the implementation easier. \"Make the change easy, then make the easy change.\"\n\n### 3. Draft vertical slices\n\nBreak the work into **tracer bullet** tickets.\n\n\u003Cvertical-slice-rules>\n\n- Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests): vertical, NOT a horizontal slice of one layer\n- A completed slice is demoable or verifiable on its own\n- Each slice is sized to fit in a single fresh context window\n- Any prefactoring should be done first\n\n\u003C\u002Fvertical-slice-rules>\n\nGive each ticket its **blocking edges**: the other tickets that must complete\nbefore it can start. Keep dependencies cycle-free. A ticket with no blockers\nuses the contribution guide's Readiness and installed parent-readiness rules.\n\n**Wide refactors are the exception to vertical slicing.** A **wide refactor** is one mechanical change (rename a column, retype a shared symbol) whose **blast radius** fans across the whole codebase, so a single edit breaks thousands of call sites at once and no vertical slice can land green. Don't force it into a tracer bullet; sequence it as **expand–contract**. First expand: add the new form beside the old so nothing breaks. Then migrate the call sites over in batches sized by blast radius (per package, per directory), each batch its own ticket blocked by the expand, keeping CI green batch to batch because the old form still exists. Finally contract: delete the old form once no caller remains, in a ticket blocked by every migrate batch. Every ticket's change merges into its base branch on its own, with its checks passing: when even the batches can't stay green alone, fold the batches that can't into one ticket.\n\n**Live acceptance is a ticket of its own.** When work must be shown on a live system, split it into a **source ticket**, which closes when its pull request merges, and a **live-acceptance ticket**, blocked by the source ticket, whose acceptance criteria are the recorded evidence that the deployed change behaves on the live system as its contract says. A merge never closes it: the source ticket's pull request links it without a closing reference, and it closes only once that evidence is recorded on it. Its live steps take the route the installed rules give work that needs host access.\n\n### 4. Prepare the split for independent review\n\nPresent the proposed breakdown as a numbered list. For each ticket, show:\n\n- **Title**: short descriptive name\n- **Blocked by**: which other tickets (if any) must complete first\n- **What it delivers**: the end-to-end behaviour this ticket makes work\n\nAttach evidence for granularity, real dependencies, independently mergeable\nslices and test seams, and identify any factual verification the independent\nreviewer must finish. Reuse recorded answers and plan approval. Read and apply\nthe contribution guide's Triage inference test, inferred-list and\nowner-question rules to unanswered choices.\n\nReturn the proposed split and evidence for the orchestrating agent's decision\nand independent acceptance under the guide's Triage rules. Use its correction\nand fact-finding routes for feedback rather than an owner breakdown quiz.\n\n### 5. Publish the tickets to the configured tracker\n\nPublish the proposed tickets awaiting review. **How** depends on the configured\ntracker; the tickets are the same either way, only the shape of the blocking\nedges changes:\n\n- **Local files** → write one file per ticket under `.scratch\u002F\u003Cfeature-slug>\u002Fissues\u002F\u003CNN>-\u003Cslug>.md`, numbered from `01` in dependency order (blockers first). Each file's \"Blocked by\" lists the numbers\u002Ftitles it depends on. Use the per-ticket file template below: one ticket per file, never a single combined file.\n- **A real issue tracker (GitHub, Linear, …)** → publish one issue per ticket in its responsible repository, in dependency order (blockers first) so each ticket's blocking edges can reference real identifiers. Link each ticket to the one specification parent and its blockers with the platform's native sub-issue and blocking relationships: the \"Parent\" and \"Blocked by\" sections restate those links for the reader and never stand in for them. If a native link can't be created, stop publication progression and report the exact missing parent\u002Fblocker relationship and platform failure. A text-only edge is never reported as established. Before publishing, read `.repo-standards\u002Frules\u002Fcomments.md#disclaimers`.\n\nUse the guide's direct-body-contract publication route. Return the proposed\nsplit, exact published contracts and established native links to the\norchestrating agent for acceptance under the guide's Triage and Readiness\nsections and the installed parent-readiness rules, including after amendments.\n\nOnce reviewed, work the **frontier**: any ready ticket whose blockers are all done. For a purely linear chain that means top to bottom.\n\nOnce a ticket is ready, nobody edits it to record progress, ticking its acceptance criteria included: progress lives in linked pull requests, sub-issue states and comments. A ticket closes when its own acceptance criteria hold.\n\nKeep the parent open. Modify its contract only for an authorized amendment;\npublication progress belongs in comments and native sub-issue states.\n\n\u003Clocal-ticket-template>\n\n# \u003CNN>: \u003CTicket title>\n\n**What to build:** the end-to-end behaviour this ticket makes work, from the user's perspective, not a layer-by-layer implementation list.\n\n**Blocked by:** the numbers\u002Ftitles of the tickets that gate this one, or \"None (readiness still required)\".\n\n**Status:** state:triage\n\n- [ ] Acceptance criterion 1\n- [ ] Acceptance criterion 2\n\n\u003C\u002Flocal-ticket-template>\n\n\u003Cissue-template>\n\n## Parent\n\nA reference to the parent issue on the tracker (if the source was an existing issue, otherwise omit this section).\n\n## What to build\n\nThe end-to-end behaviour this ticket makes work, from the user's perspective, not layer-by-layer implementation.\n\n## Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n\n## Blocked by\n\n- A reference to each blocking ticket, or \"None (readiness still required)\".\n\n\u003C\u002Fissue-template>\n\nIn either form, avoid specific file paths or code snippets: they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it and note briefly that it came from a prototype. Trim to the decision-rich parts, not a working demo, just the important bits.\n\n## Reads\n\nPaths are relative to the repository root.\n\n- `docs\u002Fagents\u002Fissue-tracker.md` and `docs\u002Fagents\u002Ftriage-labels.md`: the\n  configured tracker and its triage label vocabulary. When the tracker config\n  is missing and no tracker was provided, ask the user whether to publish to\n  local files or a real tracker; when the label config is missing, use the\n  canonical role names as the label strings.\n- `.repo-standards\u002Frules\u002Fcomments.md`: the installed comment rules, whose\n  section the posting steps name. When it is missing, post issue bodies and\n  comments as the steps describe.\n- `GLOSSARY.md` and the ADRs in `docs\u002Fadr\u002F`: the domain vocabulary and\n  decisions to respect. When either is missing, use the codebase's own words.\n- The installed rules, such as the `github-repository-configuration` rules,\n  which the `repository-standards` skill looks up: the companion labels\n  readiness needs, and the route for work that needs host access. When they\n  are missing, readiness carries no companion labels, and a live-acceptance\n  ticket takes no route of its own.\n- `.scratch\u002F`: the local-files tracker's tickets. When it is missing, create\n  it as step 5 says.\n- `CONTRIBUTING.md`: inference, split authority, amendments and readiness. If\n  missing, use `grilling`'s missing-guide fallback and independent exact-revision review, and\n  ask the user only for unresolved owner choices.\n- The `grilling` skill: the inference fallback, only when the contribution\n  guide is missing. If also missing, report it and stop for the missing policy.\n- The `to-spec` skill: publish the single specification before a grill's\n  tickets. If missing, report it and stop ticket publication until a\n  specification exists.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","448e2ed8cdf04967d08e8f682dbcb135896c8185",".repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fto-tickets","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern","https:\u002F\u002Fgithub.com\u002Flutzseverino","If Codex could write profile bios, you wouldn't be reading this. Or would you?","2026-11-15 01:04:49",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lutzseverino\u002Fpostern --skill to-tickets",{"tool":38,"command":39},"bunx","bunx skills add lutzseverino\u002Fpostern --skill to-tickets",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lutzseverino\u002Fpostern --skill to-tickets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",146,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fto-tickets\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"CREDITS.md",3099,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fto-tickets\u002FCREDITS.md",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7F4S3V789SV39G7XQQ021FS","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7F4RZQ3SV81GM59D7FCZE98","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7F4RTBB780C72G2GP3GH904","triage","Move issues and external PRs through a state machine of triage roles, sort each request by where its uncertainty lies, and bring its agent brief to acceptance through research and independent review, or through a grilling session with the owner. Also runs unattended as the factory's triage run, which writes nothing and ends with a run result.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7F4RH5ZSNGESE2ECB4JH7J7","to-spec","Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fto-spec\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7F4RF1VJMBJFQP4K974PRSZ","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7F4RCK354YDPRAS5D19W920","review","Review an implemented draft pull request as an agent that did not write it, fix small findings or hand it back, then mark it ready and babysit it to merge. Use when a draft PR waits on review, or when asked to review and land one.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[]]