[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CYAJVGQ4YYD192Z9Z4H6M8":3,"skill-same:01M6CYAJVGQ4YYD192Z9Z4H6M8":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":13,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M6CYAJVGQ4YYD192Z9Z4H6M8","report-bug",null,"Report a bug in the compound-engineering plugin","The-Rabak\u002Fnaysmith","The-Rabak","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F44833742?v=4","01M6CY211HB58Y8JNWWEV9FGN1","01M6CY8HJW3TE1AQW1F13PHYB2",0,"GPL-2.0","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Freport-bug\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[23,24,25,26,27,28],"report","bug","report bug","plugin","engineering","compound","2026-11-10 10:12:30",false,"---\nname: report-bug\ndescription: Report a bug in the compound-engineering plugin\n---\n\n## Arguments\n[optional: brief description of the bug]\n\n# Report a Compounding Engineering Plugin Bug\n\nReport bugs encountered while using the compound-engineering plugin. This command gathers structured information and prepares a bug report for the maintainer.\n\n## Step 1: Gather Bug Information\n\nUse the AskUserQuestion tool to collect the following information:\n\n**Question 1: Bug Category**\n- What type of issue are you experiencing?\n- Options: Agent not working, Command not working, Skill not working, MCP server issue, Installation problem, Other\n\n**Question 2: Specific Component**\n- Which specific component is affected?\n- Ask for the name of the agent, command, skill, or MCP server\n\n**Question 3: What Happened (Actual Behavior)**\n- Ask: \"What happened when you used this component?\"\n- Get a clear description of the actual behavior\n\n**Question 4: What Should Have Happened (Expected Behavior)**\n- Ask: \"What did you expect to happen instead?\"\n- Get a clear description of expected behavior\n\n**Question 5: Steps to Reproduce**\n- Ask: \"What steps did you take before the bug occurred?\"\n- Get reproduction steps\n\n**Question 6: Error Messages**\n- Ask: \"Did you see any error messages? If so, please share them.\"\n- Capture any error output\n\n## Step 2: Collect Environment Information\n\nAutomatically gather:\n```bash\n# Get plugin version\ncat ~\u002F.copilot\u002Fplugins\u002Finstalled_plugins.json 2>\u002Fdev\u002Fnull | grep -A5 \"compound-engineering\" | head -10 || echo \"Plugin info not found\"\n\n# Get Claude Code version\nclaude --version 2>\u002Fdev\u002Fnull || echo \"Claude CLI version unknown\"\n\n# Get OS info\nuname -a\n```\n\n## Step 3: Format the Bug Report\n\nCreate a well-structured bug report with:\n\n```markdown\n## Bug Description\n\n**Component:** [Type] - [Name]\n**Summary:** [Brief description from argument or collected info]\n\n## Environment\n\n- **Plugin Version:** [from installed_plugins.json]\n- **Claude Code Version:** [from claude --version]\n- **OS:** [from uname]\n\n## What Happened\n\n[Actual behavior description]\n\n## Expected Behavior\n\n[Expected behavior description]\n\n## Steps to Reproduce\n\n1. [Step 1]\n2. [Step 2]\n3. [Step 3]\n\n## Error Messages\n\n```\n[Any error output]\n```\n\n## Additional Context\n\n[Any other relevant information]\n\n---\n*Reported via `\u002Freport-bug` command*\n```\n\n## Step 4: Save Bug Report\n\nSave the formatted bug report so the user can file it:\n\n```bash\ncat > \u002Ftmp\u002Fbug-report.md \u003C\u003C'BUGREPORT'\n[Formatted bug report from Step 3]\nBUGREPORT\necho \"Bug report saved to \u002Ftmp\u002Fbug-report.md\"\n```\n\nInform the user:\n- \"Bug report saved to `\u002Ftmp\u002Fbug-report.md`\"\n- \"Please file this as an issue in the plugin repository or share it with the maintainer (The Rabak)\"\n\n## Output Format\n\n```\nBug report prepared!\n\nSaved to: \u002Ftmp\u002Fbug-report.md\nTitle: [compound-engineering] Bug: [description]\n\nPlease file this in the plugin repository or share with the maintainer.\nThank you for helping improve the compound-engineering plugin!\n```\n- If issue creation fails: Display the formatted report so user can manually create the issue\n- If required information is missing: Re-prompt for that specific field\n\n## Privacy Notice\n\nThis command does NOT collect:\n- Personal information\n- API keys or credentials\n- Private code from your projects\n- File paths beyond basic OS info\n\nOnly technical information about the bug is included in the report.\n","## Arguments\n[optional: brief description of the bug]\n\n# Report a Compounding Engineering Plugin Bug\n\nReport bugs encountered while using the compound-engineering plugin. This command gathers structured information and prepares a bug report for the maintainer.\n\n## Step 1: Gather Bug Information\n\nUse the AskUserQuestion tool to collect the following information:\n\n**Question 1: Bug Category**\n- What type of issue are you experiencing?\n- Options: Agent not working, Command not working, Skill not working, MCP server issue, Installation problem, Other\n\n**Question 2: Specific Component**\n- Which specific component is affected?\n- Ask for the name of the agent, command, skill, or MCP server\n\n**Question 3: What Happened (Actual Behavior)**\n- Ask: \"What happened when you used this component?\"\n- Get a clear description of the actual behavior\n\n**Question 4: What Should Have Happened (Expected Behavior)**\n- Ask: \"What did you expect to happen instead?\"\n- Get a clear description of expected behavior\n\n**Question 5: Steps to Reproduce**\n- Ask: \"What steps did you take before the bug occurred?\"\n- Get reproduction steps\n\n**Question 6: Error Messages**\n- Ask: \"Did you see any error messages? If so, please share them.\"\n- Capture any error output\n\n## Step 2: Collect Environment Information\n\nAutomatically gather:\n```bash\n# Get plugin version\ncat ~\u002F.copilot\u002Fplugins\u002Finstalled_plugins.json 2>\u002Fdev\u002Fnull | grep -A5 \"compound-engineering\" | head -10 || echo \"Plugin info not found\"\n\n# Get Claude Code version\nclaude --version 2>\u002Fdev\u002Fnull || echo \"Claude CLI version unknown\"\n\n# Get OS info\nuname -a\n```\n\n## Step 3: Format the Bug Report\n\nCreate a well-structured bug report with:\n\n```markdown\n## Bug Description\n\n**Component:** [Type] - [Name]\n**Summary:** [Brief description from argument or collected info]\n\n## Environment\n\n- **Plugin Version:** [from installed_plugins.json]\n- **Claude Code Version:** [from claude --version]\n- **OS:** [from uname]\n\n## What Happened\n\n[Actual behavior description]\n\n## Expected Behavior\n\n[Expected behavior description]\n\n## Steps to Reproduce\n\n1. [Step 1]\n2. [Step 2]\n3. [Step 3]\n\n## Error Messages\n\n```\n[Any error output]\n```\n\n## Additional Context\n\n[Any other relevant information]\n\n---\n*Reported via `\u002Freport-bug` command*\n```\n\n## Step 4: Save Bug Report\n\nSave the formatted bug report so the user can file it:\n\n```bash\ncat > \u002Ftmp\u002Fbug-report.md \u003C\u003C'BUGREPORT'\n[Formatted bug report from Step 3]\nBUGREPORT\necho \"Bug report saved to \u002Ftmp\u002Fbug-report.md\"\n```\n\nInform the user:\n- \"Bug report saved to `\u002Ftmp\u002Fbug-report.md`\"\n- \"Please file this as an issue in the plugin repository or share it with the maintainer (The Rabak)\"\n\n## Output Format\n\n```\nBug report prepared!\n\nSaved to: \u002Ftmp\u002Fbug-report.md\nTitle: [compound-engineering] Bug: [description]\n\nPlease file this in the plugin repository or share with the maintainer.\nThank you for helping improve the compound-engineering plugin!\n```\n- If issue creation fails: Display the formatted report so user can manually create the issue\n- If required information is missing: Re-prompt for that specific field\n\n## Privacy Notice\n\nThis command does NOT collect:\n- Personal information\n- API keys or credentials\n- Private code from your projects\n- File paths beyond basic OS info\n\nOnly technical information about the bug is included in the report.\n",{"name":5,"description":7},"main","b097d394a335a9ec3c8a02d64e111f1a9c96703d",".github\u002Fskills\u002Freport-bug","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith","https:\u002F\u002Fgithub.com\u002FThe-Rabak","2026-03-04 03:03:05",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add The-Rabak\u002Fnaysmith --skill report-bug",{"tool":46,"command":47},"bunx","bunx skills add The-Rabak\u002Fnaysmith --skill report-bug",{"tool":49,"command":50},"pnpm","pnpm dlx skills add The-Rabak\u002Fnaysmith --skill report-bug","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Freport-bug\u002FSKILL.md",true,[],[55,67,81,94,110,124],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":29},"01M6CYBMHFVAMC4T3J8QFYN42M","workflows-work","Execute work plans efficiently while maintaining quality and finishing features","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-work\u002FSKILL.md",[],[62,63,64,65,66],"workflows work","work","workflows","execute","quality",{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":29},"01M6CYBJ1KP7W3X8HEG49KST9Q","workflows-review","Perform exhaustive code reviews using multi-agent analysis, ultra-thinking, and worktrees","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-review\u002FSKILL.md",[],[74,64,75,76,77,78,79,80],"workflows review","review","thinking","worktrees","multi-agent","analysis","code",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":29},"01M6CYBEW8DDBXW62Q2CA29BPR","workflows-plan","Transform feature descriptions into well-structured project plans following conventions","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-plan\u002FSKILL.md",[],[64,88,89,90,91,92,93],"workflows plan","plan","project","structured","following conventions","conventions",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":105,"publishedAt":29},"01M6CYBBKAHJJ85JC2PS380TGZ","workflows-compound","Document a recently solved problem to compound your team's knowledge","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-compound\u002FSKILL.md",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[28,106,64,107,108,109],"workflows compound","document","knowledge","team",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":29},"01M6CYB9062GMP8VSA7N7PB4NW","workflows-brainstorm","Explore requirements and approaches through collaborative dialogue before planning implementation","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-brainstorm\u002FSKILL.md",[],[117,118,64,119,120,121,122,123],"workflows brainstorm","brainstorm","planning","requirements","explore","implementation","dialogue",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":29},"01M6CYB6S7GKWH62CRV3K79MHW","triage","Triage and categorize findings for the CLI todo system","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage\u002FSKILL.md",[],[126,131,132,133,134],"system","categorize","todo","cli"]