[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F54C2WT6A2VTRETYHBV7EZ":3,"skill-same:01M7F54C2WT6A2VTRETYHBV7EZ":46},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M7F54C2WT6A2VTRETYHBV7EZ","sub-bug",null,"Record a bug that QA found in a story in review or accepted: find the step that let it through, make the sub-bug with its bug.md in the folder of the story, write its four answers, and stop at the owner's approve. Use when the owner or QA reports a bug in a built story. Not for old code or a new request: \u002Fintake.","lamtran8401\u002Fnook","lamtran8401","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F91517229?v=4","01M7F5172CY814PXRBJG6TWAAC","Trần Vũ Lam","01M7F5173D7DJEW5XS3V04KC1V",0,"MIT","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fsub-bug\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: sub-bug\ndescription: \"Record a bug that QA found in a story in review or accepted: find the step that let it through, make the sub-bug with its bug.md in the folder of the story, write its four answers, and stop at the owner's approve. Use when the owner or QA reports a bug in a built story. Not for old code or a new request: \u002Fintake.\"\nargument-hint: \"\u003Cstory id> \u003Creport or ticket key>\"\ndisable-model-invocation: true\nallowed-tools: Bash(nook *), Bash(git status *), Bash(git diff *), Bash(git log *), Read, Glob, Grep, Edit, Write\n---\n\nGoal: a bug that QA found gets the step that let it through, its own fix with a test that fails first, and one row in its story.\nThe first word of the arguments is the story; the other words are the report, or the key of a ticket of the bug, such as `SHOP-31`.\nWith no story or no report, ask the owner with AskUserQuestion.\nOffer the two likeliest stories in `reviewing` or `accepted` as options, and name the others in the question.\n\n## The origin\nFind the origin from the evidence, not from the words of the report. Read the spec, the plan and the tasks of the story, then the code.\n```\norigin   when                                                   what the sub-bug adds\nbuild    a criterion of the story says it; the code misses it   a task that the story missed\nspec     the ticket wants it; no criterion of the story says it  a criterion and its task\nplan     the criteria are right; the approach is wrong           a part of the plan and its tasks\nintent   the agent read the ticket in another way than the owner the reading of the ticket\noutside  old code, or a new request                             no sub-bug: a new item\n```\nA label is optional. When `docs\u002Fbug-labels.md` exists, the label must be one of its `- label` lines, such as `edge-case`.\n\n## Order\n1. Run `nook item show \u003Cstory>`. A sub-bug needs its story in `reviewing` or `accepted`; before that, a slice of the story fixes the bug.\n2. A ticket key: get the ticket onto disk and have it read in quarantine, as steps 2 and 3 of `\u002Fintake` say. The report is the title from the summary.\n   Reproduce the bug as the craft find-cause says (`nook craft find-cause`). When it does not reproduce, report that to the owner and stop.\n3. Find the origin with the table above. Write one line of evidence: the criterion, the line of the plan, or the line of the ticket.\n   For the origin `outside`, stop. Tell the owner that `nook item new \"\u003Ctitle>\" --ticket` makes a new item.\n4. Run `nook item sub-bug \u003Cstory> \"\u003Creport>\" --origin \u003Corigin>`, with `--label \u003Clabel>` when there is one, and `--id \u003Ckey>` for a ticket of its own.\n   The sub-bug is a fix of size S in `framing`. Its file is `works\u002F\u003Cstory>\u002Fbugs\u002F\u003Cid>.md`, and the `## Sub-bugs` table of the story gets its row.\n5. Write the four answers in that file, as `\u002Fquick` says for a fix: Why, Reproduce, Actual, the criteria under `## Expected`, Fix, Impact, and T1 with the failing test.\n   For the origin `spec`, the criterion that the story missed goes under `## Expected`, with the line of the ticket as its source.\n6. Run `nook item plan \u003Cid>`, then `nook item check \u003Cid>`. Fix each gap, and check again until no gap is left.\n7. Show the file, the origin and its evidence. The owner confirms the origin at the approve. A different origin: `nook item edit \u003Cid> origin \u003Corigin>`.\n8. Report, and say: approve: type `\u002Fgate approve \u003Cid>`. Then stop.\n   After the approve, `\u002Fcook \u003Cid>` builds the sub-bug on the branch of its story. After its accept, `\u002Fpr \u003Cstory>` takes it to the PR of the story.\n\n## The report\n```\nWaits for you: approve: type \u002Fgate approve BUG-001\nBUG-001, a sub-bug of SHOP-12: an empty page shows an error. Origin spec, label edge-case.\nEvidence: the ticket asks for an empty state; no criterion of SHOP-12 names it.\nFile: works\u002FSHOP-12\u002Fbugs\u002FBUG-001.md. AC1: an empty page shows \"No shipments\". T1: the list test with no rows, which fails first.\nYour turn:\n  1. \u002Fgate approve BUG-001   start the build   (recommended)\n  2. nook item edit BUG-001 origin \u003Corigin>   another origin\n```\n\n## Gotchas\n- One cause is one sub-bug. Two reports with one cause go in one sub-bug; name both in its Why.\n- The story does not change: the sub-bug holds its criterion and its task. The row of the table is the one line in the story, and the CLI writes it.\n- The story closes only after each sub-bug is closed. A sub-bug for a later sprint leaves the story with `nook item detach \u003Cid> --reason \"\u003Cwhy>\"`.\n- The model never starts `\u002Fsub-bug`: the owner types it.\n","Goal: a bug that QA found gets the step that let it through, its own fix with a test that fails first, and one row in its story.\nThe first word of the arguments is the story; the other words are the report, or the key of a ticket of the bug, such as `SHOP-31`.\nWith no story or no report, ask the owner with AskUserQuestion.\nOffer the two likeliest stories in `reviewing` or `accepted` as options, and name the others in the question.\n\n## The origin\nFind the origin from the evidence, not from the words of the report. Read the spec, the plan and the tasks of the story, then the code.\n```\norigin   when                                                   what the sub-bug adds\nbuild    a criterion of the story says it; the code misses it   a task that the story missed\nspec     the ticket wants it; no criterion of the story says it  a criterion and its task\nplan     the criteria are right; the approach is wrong           a part of the plan and its tasks\nintent   the agent read the ticket in another way than the owner the reading of the ticket\noutside  old code, or a new request                             no sub-bug: a new item\n```\nA label is optional. When `docs\u002Fbug-labels.md` exists, the label must be one of its `- label` lines, such as `edge-case`.\n\n## Order\n1. Run `nook item show \u003Cstory>`. A sub-bug needs its story in `reviewing` or `accepted`; before that, a slice of the story fixes the bug.\n2. A ticket key: get the ticket onto disk and have it read in quarantine, as steps 2 and 3 of `\u002Fintake` say. The report is the title from the summary.\n   Reproduce the bug as the craft find-cause says (`nook craft find-cause`). When it does not reproduce, report that to the owner and stop.\n3. Find the origin with the table above. Write one line of evidence: the criterion, the line of the plan, or the line of the ticket.\n   For the origin `outside`, stop. Tell the owner that `nook item new \"\u003Ctitle>\" --ticket` makes a new item.\n4. Run `nook item sub-bug \u003Cstory> \"\u003Creport>\" --origin \u003Corigin>`, with `--label \u003Clabel>` when there is one, and `--id \u003Ckey>` for a ticket of its own.\n   The sub-bug is a fix of size S in `framing`. Its file is `works\u002F\u003Cstory>\u002Fbugs\u002F\u003Cid>.md`, and the `## Sub-bugs` table of the story gets its row.\n5. Write the four answers in that file, as `\u002Fquick` says for a fix: Why, Reproduce, Actual, the criteria under `## Expected`, Fix, Impact, and T1 with the failing test.\n   For the origin `spec`, the criterion that the story missed goes under `## Expected`, with the line of the ticket as its source.\n6. Run `nook item plan \u003Cid>`, then `nook item check \u003Cid>`. Fix each gap, and check again until no gap is left.\n7. Show the file, the origin and its evidence. The owner confirms the origin at the approve. A different origin: `nook item edit \u003Cid> origin \u003Corigin>`.\n8. Report, and say: approve: type `\u002Fgate approve \u003Cid>`. Then stop.\n   After the approve, `\u002Fcook \u003Cid>` builds the sub-bug on the branch of its story. After its accept, `\u002Fpr \u003Cstory>` takes it to the PR of the story.\n\n## The report\n```\nWaits for you: approve: type \u002Fgate approve BUG-001\nBUG-001, a sub-bug of SHOP-12: an empty page shows an error. Origin spec, label edge-case.\nEvidence: the ticket asks for an empty state; no criterion of SHOP-12 names it.\nFile: works\u002FSHOP-12\u002Fbugs\u002FBUG-001.md. AC1: an empty page shows \"No shipments\". T1: the list test with no rows, which fails first.\nYour turn:\n  1. \u002Fgate approve BUG-001   start the build   (recommended)\n  2. nook item edit BUG-001 origin \u003Corigin>   another origin\n```\n\n## Gotchas\n- One cause is one sub-bug. Two reports with one cause go in one sub-bug; name both in its Why.\n- The story does not change: the sub-bug holds its criterion and its task. The row of the table is the one line in the story, and the CLI writes it.\n- The story closes only after each sub-bug is closed. A sub-bug for a later sprint leaves the story with `nook item detach \u003Cid> --reason \"\u003Cwhy>\"`.\n- The model never starts `\u002Fsub-bug`: the owner types it.\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25,"disable-model-invocation":26},"Bash(nook *), Bash(git status *), Bash(git diff *), Bash(git log *), Read, Glob, Grep, Edit, Write","\u003Cstory id> \u003Creport or ticket key>",true,"main","0b3b58696520a442b4b4f87c1c5a5ac760c03120","plugin\u002Fskills\u002Fsub-bug","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook","https:\u002F\u002Fgithub.com\u002Flamtran8401","2026-10-27 20:01:54",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":26},[35,38,41],{"tool":36,"command":37},"npx","npx skills add lamtran8401\u002Fnook --skill sub-bug",{"tool":39,"command":40},"bunx","bunx skills add lamtran8401\u002Fnook --skill sub-bug",{"tool":42,"command":43},"pnpm","pnpm dlx skills add lamtran8401\u002Fnook --skill sub-bug","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fsub-bug\u002FSKILL.md",[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7F55NA9ZJEBZ27S3PN5ZN0J","yolo","Run an item alone from its state to the owner's accept: the lead runs the phases, records each guess, passes the plan gate with proceed, and stops at a stop rule. Use when the owner types \u002Fyolo with an id, a prompt, or nothing.","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fyolo\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7F55GE7WPQCSP3K44BEY0TE","write-walkthrough","Write walkthrough.md, the explanation of finished work: what works now in plain words, the changed files, where to start reading, the key code, the met criteria, how to try it, the risks. It is the source of the Walkthrough tab of the web app. Use after \u002Fqa, or for a question about the code.","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwrite-walkthrough\u002FSKILL.md",[],[],{"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},"01M7F55A7M9W0D5340Y4A8YFB7","wiki-tidy","Find what is wrong in the wiki: broken links, pages with no index line, lines too near the code, stale epic pages, topics with no source, two pages on one topic, adjectives with no example. Fix the mechanical part after one yes; list the rest. Use when the owner says tidy the wiki, or after many pages changed.","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwiki-tidy\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7F555A8JJHX4Q61Q06B6DBS","wiki-merge","Merge related wiki pages into one complete page: the pages of the features of one process or epic become one page with the flow from end to end. The old pages move to the archive after the owner's yes, and their links point at the new page. Use when the owner says merge these pages, or when wiki-tidy finds pages on one topic.","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwiki-merge\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7F551S3NHQ0JVT0KGM36WPQ","wiki-ask","Answer a question from the wiki: the index first, then only the pages whose line matches, an answer in a few lines with a link to each page. Use when the owner asks what the wiki says, or asks why or how about a known topic. Not to add a page: wiki-add.","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwiki-ask\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7F54XC5YQK6KVXJVPZ6NDM4","wiki-add","Keep the lesson of a source in the wiki: a page in the shelf business\u002F or tech\u002F with its main points, a real example for each, the gotchas and the link of the source; written after the owner's yes. Use when the owner says add this to the wiki, keep this, or gives a PRD, a ticket, notes or an article to keep.","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwiki-add\u002FSKILL.md",[],[]]