[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVCMQFVPF79JYGPNC68AES":3,"skill-same:01M7CVCMQFVPF79JYGPNC68AES":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":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M7CVCMQFVPF79JYGPNC68AES","report-issue",null,"File a bug, feature, or deprecation ticket on this repo from a quick notice.","TudeOrangBiasa\u002Fskills-for-agents","TudeOrangBiasa","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F125188681?v=4","01M7CV804RMMCVN5M0D4ZCQ6D8","TudeStillLearning!","01M7CV805CRFTQY48WZ6JK57YK",1,"MIT","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Freport-issue\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"File a bug, feature, or deprecation ticket on this repo from a quick notice.\"\ndisable-model-invocation: true\nname: report-issue\n---\n\n# Report issue\n\nYou noticed something worth fixing or building in the skills-for-agents repo (TudeOrangBiasa\u002Fskills-for-agents, https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fissues). This skill turns the notice into one ticket on that tracker, using the template that fits (bug, feature, deprecation). One notice is one ticket with one type. Never file a bare complaint: every ticket carries a repro or a what-to-build plus testable acceptance, or it stays unsent.\n\n## What it does\n\nTakes a rough notice (\"X looks broken\", \"we should add Y\", \"Z is dead weight\") and produces a filed ticket with the right template fields filled: type, repro or what-to-build, Kompleksitas, acceptance, parent and blocked-by where they exist. The defining constraint: the interview that fills the template happens before any `gh` call, so the tracker never receives a foggy ticket.\n\n## When to reach for it\n\nYou invoke this by typing `\u002Freport-issue`, and the agent will not reach for it on its own. Reach for this when you spot a defect, a missing behavior, or dead weight in this repo and want it tracked with repro plus acceptance. For working an existing backlog instead, use `ship-triage`.\n\n## Pick the template first\n\nMatch the notice to one template in `.github\u002FISSUE_TEMPLATE\u002F`, never blend them:\n\n1. Something broken: `bug.yml`. Needs perilaku sekarang vs yang diharapkan plus langkah repro minimal.\n2. Something new or better: `feature.yml`. Needs what to build as end-to-end behavior plus optional risk with one RISK rule.\n3. Something to remove: `deprecation.yml`. Needs what gets removed, its replacement, plus proof the removal is clean (grep yang harus kosong, link yang harus resolve).\n\n## Interview before filing\n\nAsk only for the fields the chosen template requires and the notice did not supply yet. One round at a time, concrete questions, no padding. Required in every ticket: one `## Kompleksitas` line (the repo term, spelled with K; files plus verification steps, e.g. O(1) file, 1 repro test) and testable acceptance criteria (what gets verified and how). A ticket missing either stays a draft in chat, never filed.\n\nFor a bug, verify the claim first when the repro is cheap: check the code path or run the failing step. Say confirmed with the path, or failed, or needs detail. For a feature, check redundancy first: search for an existing implementation by domain concept. If built already, say so and file nothing.\n\n## File it\n\nTarget the skills-for-agents tracker explicitly: every `gh` call passes `--repo TudeOrangBiasa\u002Fskills-for-agents`, because this skill may run from a consumer repo checkout. Duplicate search is scoped there too (`gh issue list --repo ... --search ...`), never the current directory remote. Create one issue with `gh issue create --repo TudeOrangBiasa\u002Fskills-for-agents`, title prefixed `[bug]:`, `[feat]:`, or `[deprecate]:` per template, labels from the template (`needs-triage`, `risk:low`; raise risk only with evidence). Report back the issue URL plus number. Never batch two notices into one ticket; never open a PR from here (that is `whips` work once triage ripens it).\n\n## Common questions\n\n**Does this replace ship-triage?**\nNo. This files the ticket; `ship-triage` ripens it to agent-ready. Filed tickets land in `needs-triage` by default.\n\n**What if the notice is already tracked?**\nSearch open issues first by concept, not wording. If found, point at it and file nothing.\n\n**What if I am unsure about Kompleksitas?**\nEstimate in verification steps (files touched, tests run, gh calls). One honest line beats a precise-looking fiction.\n\n## It's working if\n\n1. Every filed ticket has a repro or what-to-build plus acceptance, checkable on the issue page.\n2. No ticket lands without a Kompleksitas line.\n3. Duplicates get pointed at instead of filed twice.\n\n## Where it fits\n\nRole: standalone reach-for-it-anytime reporter feeding the triage queue (`report-issue` files, `ship-triage` ripens, `whips` builds). Neighbours: `ship-triage` because it consumes what this files, linked repo-relatively at [ship-triage](..\u002Fship-triage\u002FSKILL.md); `plan-tickets` because multi-ticket breakdowns belong there, linked at [plan-tickets](..\u002Fplan-tickets\u002FSKILL.md). The map: [guide](..\u002Fguide\u002FSKILL.md).\n","# Report issue\n\nYou noticed something worth fixing or building in the skills-for-agents repo (TudeOrangBiasa\u002Fskills-for-agents, https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fissues). This skill turns the notice into one ticket on that tracker, using the template that fits (bug, feature, deprecation). One notice is one ticket with one type. Never file a bare complaint: every ticket carries a repro or a what-to-build plus testable acceptance, or it stays unsent.\n\n## What it does\n\nTakes a rough notice (\"X looks broken\", \"we should add Y\", \"Z is dead weight\") and produces a filed ticket with the right template fields filled: type, repro or what-to-build, Kompleksitas, acceptance, parent and blocked-by where they exist. The defining constraint: the interview that fills the template happens before any `gh` call, so the tracker never receives a foggy ticket.\n\n## When to reach for it\n\nYou invoke this by typing `\u002Freport-issue`, and the agent will not reach for it on its own. Reach for this when you spot a defect, a missing behavior, or dead weight in this repo and want it tracked with repro plus acceptance. For working an existing backlog instead, use `ship-triage`.\n\n## Pick the template first\n\nMatch the notice to one template in `.github\u002FISSUE_TEMPLATE\u002F`, never blend them:\n\n1. Something broken: `bug.yml`. Needs perilaku sekarang vs yang diharapkan plus langkah repro minimal.\n2. Something new or better: `feature.yml`. Needs what to build as end-to-end behavior plus optional risk with one RISK rule.\n3. Something to remove: `deprecation.yml`. Needs what gets removed, its replacement, plus proof the removal is clean (grep yang harus kosong, link yang harus resolve).\n\n## Interview before filing\n\nAsk only for the fields the chosen template requires and the notice did not supply yet. One round at a time, concrete questions, no padding. Required in every ticket: one `## Kompleksitas` line (the repo term, spelled with K; files plus verification steps, e.g. O(1) file, 1 repro test) and testable acceptance criteria (what gets verified and how). A ticket missing either stays a draft in chat, never filed.\n\nFor a bug, verify the claim first when the repro is cheap: check the code path or run the failing step. Say confirmed with the path, or failed, or needs detail. For a feature, check redundancy first: search for an existing implementation by domain concept. If built already, say so and file nothing.\n\n## File it\n\nTarget the skills-for-agents tracker explicitly: every `gh` call passes `--repo TudeOrangBiasa\u002Fskills-for-agents`, because this skill may run from a consumer repo checkout. Duplicate search is scoped there too (`gh issue list --repo ... --search ...`), never the current directory remote. Create one issue with `gh issue create --repo TudeOrangBiasa\u002Fskills-for-agents`, title prefixed `[bug]:`, `[feat]:`, or `[deprecate]:` per template, labels from the template (`needs-triage`, `risk:low`; raise risk only with evidence). Report back the issue URL plus number. Never batch two notices into one ticket; never open a PR from here (that is `whips` work once triage ripens it).\n\n## Common questions\n\n**Does this replace ship-triage?**\nNo. This files the ticket; `ship-triage` ripens it to agent-ready. Filed tickets land in `needs-triage` by default.\n\n**What if the notice is already tracked?**\nSearch open issues first by concept, not wording. If found, point at it and file nothing.\n\n**What if I am unsure about Kompleksitas?**\nEstimate in verification steps (files touched, tests run, gh calls). One honest line beats a precise-looking fiction.\n\n## It's working if\n\n1. Every filed ticket has a repro or what-to-build plus acceptance, checkable on the issue page.\n2. No ticket lands without a Kompleksitas line.\n3. Duplicates get pointed at instead of filed twice.\n\n## Where it fits\n\nRole: standalone reach-for-it-anytime reporter feeding the triage queue (`report-issue` files, `ship-triage` ripens, `whips` builds). Neighbours: `ship-triage` because it consumes what this files, linked repo-relatively at [ship-triage](..\u002Fship-triage\u002FSKILL.md); `plan-tickets` because multi-ticket breakdowns belong there, linked at [plan-tickets](..\u002Fplan-tickets\u002FSKILL.md). The map: [guide](..\u002Fguide\u002FSKILL.md).\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","d26d63fb9a1a8091ba1d908b1b35738b60e8be79","skills\u002Fuser-invoked\u002Freport-issue",0,"https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa","2026-11-05 23:44:38",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add TudeOrangBiasa\u002Fskills-for-agents --skill report-issue",{"tool":38,"command":39},"bunx","bunx skills add TudeOrangBiasa\u002Fskills-for-agents --skill report-issue",{"tool":41,"command":42},"pnpm","pnpm dlx skills add TudeOrangBiasa\u002Fskills-for-agents --skill report-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Freport-issue\u002FSKILL.md",[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",148,"https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Freport-issue\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"CREDITS.md",293,"https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Freport-issue\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},"01M7CVDKFYKNEY024TK36QAA2R","whips","Route any non-trivial task through one entry: match a playbook, drive HIT skills plus subagents, open a reviewed ready PR with ship-pr-shaped evidence.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fwhips\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},"01M7CVDFG46BBHV71Q5JVZ7XZT","verify-upkeep","Periodic upkeep for a project's verification skill: source wave plus live pass per feature, at most one PR of proven corrections. Use to audit the verify skill.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fverify-upkeep\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},"01M7CVDB20QNGAPR8T5YXDRNT9","verify-statechart","Check a TLA+ model of a system that moves between states, such as a product flow, a protocol, or a service, and draw it as a Mermaid statechart. The report gives the shortest path to each state that breaks a rule. Use to show a bug as a path through states.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fverify-statechart\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},"01M7CVD6Y3W2A12ZDEQBS39QPD","verify-new","Generate a project-local skill that drives the app like a user (launch, doctor, drive, evidence, feature map), proven once. Use when a project has no scripted proof.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fverify-new\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},"01M7CVD2WTQ83ETMQ82GWWZAAV","ship-triage","Move issues and external PRs through a state machine of triage roles, categorise, verify, interview if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fship-triage\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},"01M7CVCYS0S8S8XW68V819QKZ6","ship-runner","Run ready-for-agent issue queues on any schedule through \u002Fwhips intake, one fresh worktree each, landing per risk tier, with the agent and model you pick at setup.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fship-runner\u002FSKILL.md",[],[]]