[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K7MPN2FG6M6JQFWFR18CJ0":3,"skill-same:01M6K7MPN2FG6M6JQFWFR18CJ0":51},{"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":24,"linkOnly":25,"markdownContent":26,"markdownBody":27,"frontMatter":28,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M6K7MPN2FG6M6JQFWFR18CJ0","todo",null,"Add a new bug or todo to the project's tracker","joewalnes\u002Fskills","joewalnes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F48950?v=4","01M6K7J46C00DDV34GMGT2NK72","Joe Walnes","01M6K7J4ANFVAP1P9ZJ3K4F3P2",3,"MIT","https:\u002F\u002Fgithub.com\u002Fjoewalnes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftodo\u002FSKILL.md",[],[5,19,20,21,22,23],"bug","tracker","task","project","add","2026-11-10 10:12:30",false,"---\nname: todo\ndescription: Add a new bug or todo to the project's tracker\nargument-hint: \u003Cdescription of the bug or task>\n---\n\n# Add Bug \u002F Todo\n\nAdd a well-written bug or task to the project's tracker. Takes a short description, enriches it with codebase context, assigns an appropriate priority, and commits.\n\n## How to Invoke\n\n```\n\u002Ftodo something is broken when I do X\n\u002Fbug the file tree flickers on resize\n\u002Ftodo add support for multiple cursors\n```\n\nThe argument is a rough description. You will enrich it into a proper bug entry.\n\n---\n\n## Step 1: Find the Tracker\n\nLocate the project's bug\u002Ftodo tracker. Check in order:\n\n1. **Local files**: Look for `bugs.md`, `BUGS.md`, `TODO.md`, `todo.md`, `ISSUES.md`, or similar in the repo root and `docs\u002F` directory\n2. **Project instructions**: Read `CLAUDE.md`, `CONTRIBUTING.md`, `README.md` for pointers to where bugs are tracked\n3. **GitHub Issues**: Run `gh issue list --state open --limit 5` to check if the project uses GitHub Issues\n\nIf no tracker is found, ask the user where to put it.\n\nRemember which tracker type you found (file or GitHub Issues) for Step 4.\n\n---\n\n## Step 2: Read the Tracker\n\nRead the existing tracker to understand:\n- **Format**: How are entries structured? What fields are used? (priority, status, tags, etc.)\n- **Conventions**: How are entries written? What tone, level of detail, formatting?\n- **Priority scheme**: What priority levels exist? (P0-P3, critical\u002Fhigh\u002Fmedium\u002Flow, etc.)\n- **Sections**: Is the file organized into sections? Where should the new entry go?\n\nMatch the existing style exactly. Do not invent new formatting.\n\n---\n\n## Step 3: Write the Entry\n\nTake the user's rough description and write a proper tracker entry:\n\n1. **Understand the issue**: Use Grep\u002FGlob\u002FRead to find the relevant code. Understand what the user is describing — find the actual file, function, or behavior involved.\n\n2. **Assign priority**: Based on impact and the project's priority scheme:\n   - **P0**: Data loss, crash, fundamentally broken core functionality\n   - **P1**: Significant usability issue, feature doesn't work as expected\n   - **P2**: Polish — inconsistency, visual glitch, minor misbehavior\n   - **P3**: Cosmetic, edge case, nice-to-have improvement\n\n   When in doubt, lean toward the higher priority (more severe). Users report things because they matter to them.\n\n3. **Write clearly**: The entry should include:\n   - A concise title that describes the problem or desired behavior\n   - Enough context for someone unfamiliar to understand the issue\n   - Specific file\u002Ffunction references if you found relevant code\n   - Expected vs actual behavior for bugs\n   - Do NOT include a fix or solution — just describe the problem\n\n4. **Match format**: Use the exact same markdown structure, heading level, and field names as existing entries in the tracker.\n\n---\n\n## Step 4: Save and Commit\n\n### If file-based tracker:\n\n1. Append the new entry to the appropriate section of the file\n2. Stage ONLY the tracker file (not other uncommitted changes):\n   ```\n   git add bugs.md   # or whatever the file is\n   ```\n3. Commit with a clear message:\n   ```\n   git commit -m \"Add P2 bug: \u003Cshort description>\"\n   ```\n4. Push:\n   ```\n   git push\n   ```\n\n### If GitHub Issues:\n\n1. Create the issue using `gh issue create`:\n   ```\n   gh issue create --title \"\u003Ctitle>\" --body \"\u003Cbody>\"\n   ```\n2. Apply appropriate labels if the project uses them\n\n---\n\n## Step 5: Confirm\n\nTell the user:\n- What was added (show the entry)\n- What priority was assigned and why\n- Where it was added (file + section, or GitHub issue URL)\n\n---\n\n## Guidelines\n\n- **Don't over-write.** A bug entry is 2-5 lines, not an essay. Match the project's existing verbosity level.\n- **Don't diagnose.** Describe the problem, not the solution. Leave root cause analysis for when the bug is being fixed.\n- **Don't duplicate.** Scan existing entries to make sure this isn't already tracked. If it is, tell the user and point them to the existing entry.\n- **Feature vs bug.** If the user describes a new feature rather than a bug, that's fine — add it under the appropriate section (many trackers have a \"Feature requests\" section). Adjust the title accordingly.\n- **Priority is a judgment call.** If the user says \"this is critical\" or \"minor thing\", respect their assessment. Otherwise, use your best judgment based on impact.\n","# Add Bug \u002F Todo\n\nAdd a well-written bug or task to the project's tracker. Takes a short description, enriches it with codebase context, assigns an appropriate priority, and commits.\n\n## How to Invoke\n\n```\n\u002Ftodo something is broken when I do X\n\u002Fbug the file tree flickers on resize\n\u002Ftodo add support for multiple cursors\n```\n\nThe argument is a rough description. You will enrich it into a proper bug entry.\n\n---\n\n## Step 1: Find the Tracker\n\nLocate the project's bug\u002Ftodo tracker. Check in order:\n\n1. **Local files**: Look for `bugs.md`, `BUGS.md`, `TODO.md`, `todo.md`, `ISSUES.md`, or similar in the repo root and `docs\u002F` directory\n2. **Project instructions**: Read `CLAUDE.md`, `CONTRIBUTING.md`, `README.md` for pointers to where bugs are tracked\n3. **GitHub Issues**: Run `gh issue list --state open --limit 5` to check if the project uses GitHub Issues\n\nIf no tracker is found, ask the user where to put it.\n\nRemember which tracker type you found (file or GitHub Issues) for Step 4.\n\n---\n\n## Step 2: Read the Tracker\n\nRead the existing tracker to understand:\n- **Format**: How are entries structured? What fields are used? (priority, status, tags, etc.)\n- **Conventions**: How are entries written? What tone, level of detail, formatting?\n- **Priority scheme**: What priority levels exist? (P0-P3, critical\u002Fhigh\u002Fmedium\u002Flow, etc.)\n- **Sections**: Is the file organized into sections? Where should the new entry go?\n\nMatch the existing style exactly. Do not invent new formatting.\n\n---\n\n## Step 3: Write the Entry\n\nTake the user's rough description and write a proper tracker entry:\n\n1. **Understand the issue**: Use Grep\u002FGlob\u002FRead to find the relevant code. Understand what the user is describing — find the actual file, function, or behavior involved.\n\n2. **Assign priority**: Based on impact and the project's priority scheme:\n   - **P0**: Data loss, crash, fundamentally broken core functionality\n   - **P1**: Significant usability issue, feature doesn't work as expected\n   - **P2**: Polish — inconsistency, visual glitch, minor misbehavior\n   - **P3**: Cosmetic, edge case, nice-to-have improvement\n\n   When in doubt, lean toward the higher priority (more severe). Users report things because they matter to them.\n\n3. **Write clearly**: The entry should include:\n   - A concise title that describes the problem or desired behavior\n   - Enough context for someone unfamiliar to understand the issue\n   - Specific file\u002Ffunction references if you found relevant code\n   - Expected vs actual behavior for bugs\n   - Do NOT include a fix or solution — just describe the problem\n\n4. **Match format**: Use the exact same markdown structure, heading level, and field names as existing entries in the tracker.\n\n---\n\n## Step 4: Save and Commit\n\n### If file-based tracker:\n\n1. Append the new entry to the appropriate section of the file\n2. Stage ONLY the tracker file (not other uncommitted changes):\n   ```\n   git add bugs.md   # or whatever the file is\n   ```\n3. Commit with a clear message:\n   ```\n   git commit -m \"Add P2 bug: \u003Cshort description>\"\n   ```\n4. Push:\n   ```\n   git push\n   ```\n\n### If GitHub Issues:\n\n1. Create the issue using `gh issue create`:\n   ```\n   gh issue create --title \"\u003Ctitle>\" --body \"\u003Cbody>\"\n   ```\n2. Apply appropriate labels if the project uses them\n\n---\n\n## Step 5: Confirm\n\nTell the user:\n- What was added (show the entry)\n- What priority was assigned and why\n- Where it was added (file + section, or GitHub issue URL)\n\n---\n\n## Guidelines\n\n- **Don't over-write.** A bug entry is 2-5 lines, not an essay. Match the project's existing verbosity level.\n- **Don't diagnose.** Describe the problem, not the solution. Leave root cause analysis for when the bug is being fixed.\n- **Don't duplicate.** Scan existing entries to make sure this isn't already tracked. If it is, tell the user and point them to the existing entry.\n- **Feature vs bug.** If the user describes a new feature rather than a bug, that's fine — add it under the appropriate section (many trackers have a \"Feature requests\" section). Adjust the title accordingly.\n- **Priority is a judgment call.** If the user says \"this is critical\" or \"minor thing\", respect their assessment. Otherwise, use your best judgment based on impact.\n",{"name":5,"description":7,"argument-hint":29},"\u003Cdescription of the bug or task>","main","0d32bda2cb8e014372c2814f5aa47f48eee0f411","skills\u002Ftodo","https:\u002F\u002Fgithub.com\u002Fjoewalnes\u002Fskills","https:\u002F\u002Fgithub.com\u002Fjoewalnes","Experimental Projects @ Stripe.\r\n\r\nPreviously: Apple, Google, ThoughtWorks, DRW, Startups.","2026-09-09 00:56:55",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add joewalnes\u002Fskills --skill todo",{"tool":43,"command":44},"bunx","bunx skills add joewalnes\u002Fskills --skill todo",{"tool":46,"command":47},"pnpm","pnpm dlx skills add joewalnes\u002Fskills --skill todo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjoewalnes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftodo\u002FSKILL.md",true,[],[52,68,87,103,109,115],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":24},"01M6K7MSG99DXYKTVVFGZWND1S","tool-web","Build a lightweight single-file web application with no external dependencies","https:\u002F\u002Fgithub.com\u002Fjoewalnes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftool-web\u002FSKILL.md",[],[59,60,61,62,63,64,65,66,67],"web","tool","tool web","single-file","with","application","dependencies","build","file",{"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":24},"01M6K7MGQFFYCD8HFDP1B95KDN","slop","Find unchosen code — surface area growing without leverage. Use pre-merge on a branch, or to check if a repo is accreting.","https:\u002F\u002Fgithub.com\u002Fjoewalnes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fslop\u002FSKILL.md",[],[70,75,76,77,78,79,80,81,82,83,84,85,86],"leverage","merge","code","explain","find","branch","repo","check","use","quick","rev","pre-merge",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":24},"01M6K7MCVREA4NZ46Q9JWZJ7TG","sitrep","Where were we? Branch, in-progress work, blocked agents, inbox, next steps. Use when resuming a session.","https:\u002F\u002Fgithub.com\u002Fjoewalnes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fsitrep\u002FSKILL.md",[],[89,94,95,96,97,98,99,80,100,101,83,102],"progress","next steps","inbox","Bash","grep","work","read","session","next",{"skillNo":104,"name":105,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":24},"01M6K7M99FYMH9SFSEKB718J2B","scorecard","https:\u002F\u002Fgithub.com\u002Fjoewalnes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fscorecard\u002FSKILL.md",[],[105],{"skillNo":110,"name":111,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":24},"01M6K7M4HNZR34GSB3V14KVCWA","retro","https:\u002F\u002Fgithub.com\u002Fjoewalnes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fretro\u002FSKILL.md",[],[111],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":24},"01M6K7M0QT6PD1SPE282ZQ0SM4","request","Ask another project's agents for a change instead of editing their repo. Use when a fix belongs in another repository.","https:\u002F\u002Fgithub.com\u002Fjoewalnes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Frequest\u002FSKILL.md",[],[117,122,96,123,124,81,125,126,83,127,128,22,129,130],"for","repository","editing","ask","fix","show","done","id","change"]