[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7347KSG4BWFG8PR9ZM79SCY":3,"skill-same:01M7347KSG4BWFG8PR9ZM79SCY":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7347KSG4BWFG8PR9ZM79SCY","issue",null,"Create or revise a GitHub issue.","notambourine\u002Fagent-plugins","notambourine","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F275093837?v=4","01M73473A77QWEA6JAW70BW4EV","01M73473AYDJYB0N74RR3B8YJS",2,"MIT","https:\u002F\u002Fgithub.com\u002Fnotambourine\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnt-dev\u002Fskills\u002Fissue\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: issue\ndescription: Create or revise a GitHub issue.\nallowed-tools: Bash, Read, Grep, Glob\nargument-hint: \"[issue-number-to-edit]\"\n---\n\n# GitHub issue\n\nWrite an issue a PM can act on: the outcome, what it covers, and how to tell it is done.\n\n## Template\n\nWork in the target repo with authenticated `gh`. Read its recent issues for conventions,\nmilestones, labels, projects, and hierarchy. Labels and milestones are per repo, so never\ncarry metadata across projects.\n\nFill the target repo's committed form or template from `.github\u002FISSUE_TEMPLATE\u002F` or\n`.github\u002Fissue_template.md`, keeping its headings exactly. Without one, use\n[.github\u002Fissue_template.md](.github\u002Fissue_template.md).\n\n## Body\n\nWrite BLUF (bottom line up front): the title and the body's first sentence state the\noutcome, so a PM who reads only those can triage. A title that names the activity or the\nmechanism fails that test. The body covers the problem, scope, constraints, context, and\nan acceptance check someone can observe. Put user behavior and business rules first. Add\nimplementation only when it is already decided or would be costly to rediscover. Link\ndecisions instead of repeating them.\n\nA ticket moved from Asana, Jira, Slack, or a meeting carries only what the source and the\nuser state. Turn every gap into an open question. Never fill one with invented scope,\nacceptance, settings, or configurability. The issue's readers cannot open an attachment\nbehind a login, such as an Asana `get_asset` or Jira link, so never link one. Download it\nand upload it per\n[..\u002Fpr\u002Freferences\u002Fgithub-attachments.md](..\u002Fpr\u002Freferences\u002Fgithub-attachments.md), or say\nthat it is missing.\n\nDesign work swaps the headings for four bold leads:\n\n- `**Goal:**` the result in one sentence.\n- `**Context:**` the design reference, plus `Replaces:` and `Figma:` URLs when they exist.\n- `**Dev Notes:**` the verified component or token to reuse, cited as `path\u002Fto\u002FFile.tsx`.\n  Never empty.\n- `**Done when:**` the route, theme, and design result someone can observe.\n\nEngineering work keeps the headings. Open with dated measurements, then the constraint,\nthen the target state. Cite `file.ts:155` only where the implementer would otherwise\nrediscover it. Use at most one table or diagram. Name prerequisites and open questions.\n\nLeave out delivery plans, tutorials, speculative solutions, and recaps. Show hierarchy\nwith child issues and parent links, and keep it out of the body.\n\n## Submit\n\nFollow [..\u002Fpr\u002Freferences\u002Fbody.md](..\u002Fpr\u002Freferences\u002Fbody.md) for wording and for where the\nbody file goes.\n\nSet only the milestone, labels, fields, status, and parent the repo uses. Keep duplicated\nmetadata consistent. A revision folds new facts into the body; a comment records only a\ndated decision or result.\n","# GitHub issue\n\nWrite an issue a PM can act on: the outcome, what it covers, and how to tell it is done.\n\n## Template\n\nWork in the target repo with authenticated `gh`. Read its recent issues for conventions,\nmilestones, labels, projects, and hierarchy. Labels and milestones are per repo, so never\ncarry metadata across projects.\n\nFill the target repo's committed form or template from `.github\u002FISSUE_TEMPLATE\u002F` or\n`.github\u002Fissue_template.md`, keeping its headings exactly. Without one, use\n[.github\u002Fissue_template.md](.github\u002Fissue_template.md).\n\n## Body\n\nWrite BLUF (bottom line up front): the title and the body's first sentence state the\noutcome, so a PM who reads only those can triage. A title that names the activity or the\nmechanism fails that test. The body covers the problem, scope, constraints, context, and\nan acceptance check someone can observe. Put user behavior and business rules first. Add\nimplementation only when it is already decided or would be costly to rediscover. Link\ndecisions instead of repeating them.\n\nA ticket moved from Asana, Jira, Slack, or a meeting carries only what the source and the\nuser state. Turn every gap into an open question. Never fill one with invented scope,\nacceptance, settings, or configurability. The issue's readers cannot open an attachment\nbehind a login, such as an Asana `get_asset` or Jira link, so never link one. Download it\nand upload it per\n[..\u002Fpr\u002Freferences\u002Fgithub-attachments.md](..\u002Fpr\u002Freferences\u002Fgithub-attachments.md), or say\nthat it is missing.\n\nDesign work swaps the headings for four bold leads:\n\n- `**Goal:**` the result in one sentence.\n- `**Context:**` the design reference, plus `Replaces:` and `Figma:` URLs when they exist.\n- `**Dev Notes:**` the verified component or token to reuse, cited as `path\u002Fto\u002FFile.tsx`.\n  Never empty.\n- `**Done when:**` the route, theme, and design result someone can observe.\n\nEngineering work keeps the headings. Open with dated measurements, then the constraint,\nthen the target state. Cite `file.ts:155` only where the implementer would otherwise\nrediscover it. Use at most one table or diagram. Name prerequisites and open questions.\n\nLeave out delivery plans, tutorials, speculative solutions, and recaps. Show hierarchy\nwith child issues and parent links, and keep it out of the body.\n\n## Submit\n\nFollow [..\u002Fpr\u002Freferences\u002Fbody.md](..\u002Fpr\u002Freferences\u002Fbody.md) for wording and for where the\nbody file goes.\n\nSet only the milestone, labels, fields, status, and parent the repo uses. Keep duplicated\nmetadata consistent. A revision folds new facts into the body; a comment records only a\ndated decision or result.\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":24},"Bash, Read, Grep, Glob","[issue-number-to-edit]","main","4a72cb32978e2633c4e0679572968456dff47707","plugins\u002Fnt-dev\u002Fskills\u002Fissue",0,"https:\u002F\u002Fgithub.com\u002Fnotambourine\u002Fagent-plugins","https:\u002F\u002Fgithub.com\u002Fnotambourine","https:\u002F\u002Fnotambourine.com\u002F","A boutique AI-native engineering agency","2026-11-12 23:38:28",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add notambourine\u002Fagent-plugins --skill issue",{"tool":40,"command":41},"bunx","bunx skills add notambourine\u002Fagent-plugins --skill issue",{"tool":43,"command":44},"pnpm","pnpm dlx skills add notambourine\u002Fagent-plugins --skill issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnotambourine\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnt-dev\u002Fskills\u002Fissue\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},".github\u002Fissue_template.md","REFERENCE","参考文档",427,"https:\u002F\u002Fgithub.com\u002Fnotambourine\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnt-dev\u002Fskills\u002Fissue\u002F.github\u002Fissue_template.md",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7348W9QJ1YT3H1M1VR90K4P","human-voice","Humanize prose by choosing a surgical voice edit or a structural rewrite. Use for AI-sounding drafts, anti-slop passes, editorial reviews, and requests to preserve an author's voice.","https:\u002F\u002Fgithub.com\u002Fnotambourine\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnt-voice\u002Fskills\u002Fhuman-voice\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M7348RS0WWS16MTEHKHV54JP","install-anti-slop","Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository. Use whenever a user asks to add anti-slop lint rules, copy the anti-slop plugin, configure opinionated Oxlint rules, or migrate an existing local anti-slop setup.","https:\u002F\u002Fgithub.com\u002Fnotambourine\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnt-vendor\u002Fskills\u002Finstall-anti-slop\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M7348Q2FDZX3EBHYSDXGZSBQ","improve-codebase-architecture","Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.","https:\u002F\u002Fgithub.com\u002Fnotambourine\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnt-vendor\u002Fskills\u002Fimprove-codebase-architecture\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7348NKZ61680RWM1RW8WDBZ","eli5","Explain a topic like I'm a 5 year old. Use when the user types \u002Feli5 \u003Ctopic> or asks for a dead-simple picture explainer of how something works.","https:\u002F\u002Fgithub.com\u002Fnotambourine\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnt-vendor\u002Fskills\u002Feli5\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M7348J36D3P7A73TPW0AJQ3Z","codebase-design","Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.","https:\u002F\u002Fgithub.com\u002Fnotambourine\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnt-vendor\u002Fskills\u002Fcodebase-design\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M7348F5KM8PGZFCAAJGM8HFS","audit-codebase","Read-only whole-codebase audit for simplifications in data structures, state representation, control flow, algorithms, and ownership. Inventories every subsystem as a coverage contract, reviews each one in a bounded subagent, verifies each finding against the repo, then audits its own coverage. Never edits, runs tests, commits, or pushes. Use for \"audit this codebase\", \"find simplifications\", or a pre-refactor survey.","https:\u002F\u002Fgithub.com\u002Fnotambourine\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnt-vendor\u002Fskills\u002Faudit-codebase\u002FSKILL.md",[],[]]