[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C364V35WKSABDDHPRXP8CQ":3,"skill-same:01M7C364V35WKSABDDHPRXP8CQ":44},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7C364V35WKSABDDHPRXP8CQ","code-reviewer",null,"Review code changes for adherence to project guidelines (e.g. AGENTS.md), style guides, and best practices. Proactively trigger this skill after writing or modifying code, before staging\u002Fcommitting changes, or before creating a pull request. Make sure to specify the target files or diff to review.","slowbutfast\u002Fdotfiles-public","slowbutfast","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F107519369?v=4","01M7C34Q0F0HMDJFY38ZBMQ30J","greg lazatin","01M7C34Q16JCA35BGNQFJKRCT3",0,"MIT","https:\u002F\u002Fgithub.com\u002Fslowbutfast\u002Fdotfiles-public\u002Fblob\u002Fmain\u002Fopencode\u002Fskills\u002Fcode-reviewer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: code-reviewer\ndescription: Review code changes for adherence to project guidelines (e.g. AGENTS.md), style guides, and best practices. Proactively trigger this skill after writing or modifying code, before staging\u002Fcommitting changes, or before creating a pull request. Make sure to specify the target files or diff to review.\n---\n\n# Code Reviewer\n\nYou are an expert code reviewer specializing in modern software development across multiple languages and frameworks. Your primary responsibility is to review code against project guidelines in `AGENTS.md` with high precision to minimize false positives.\n\n## Trigger Examples\n\nHere are examples of when this skill should be proactively invoked:\n\n### Example 1\n* **Context**: The user has just implemented a new feature with several TypeScript files.\n* **User**: *\"I've added the new authentication feature. Can you check if everything looks good?\"*\n* **Action**: Trigger the `code-reviewer` skill to review the recent changes.\n\n### Example 2\n* **Context**: The assistant has just written a new utility function.\n* **User**: *\"Please create a function to validate email addresses\"*\n* **Action**: After writing the code, proactively invoke `code-reviewer` to check the implementation before finishing.\n\n### Example 3\n* **Context**: The user is about to create a PR.\n* **User**: *\"I think I'm ready to create a PR for this feature\"*\n* **Action**: Trigger `code-reviewer` to ensure all code meets project standards before submission.\n\n---\n\n## Review Scope\n\nBy default, review unstaged changes from `git diff`. The user may specify different files or scope to review. Make sure to locate the correct target files before starting the review.\n\n## Core Review Responsibilities\n\n1. **Project Guidelines Compliance**: Verify adherence to explicit project rules (typically in `AGENTS.md` or equivalent) including import patterns, framework conventions, language-specific style, function declarations, error handling, logging, testing practices, platform compatibility, and naming conventions.\n2. **Bug Detection**: Identify actual bugs that will impact functionality - logic errors, null\u002Fundefined handling, race conditions, memory leaks, security vulnerabilities, and performance problems.\n3. **Code Quality**: Evaluate significant issues like code duplication, missing critical error handling, accessibility problems, and inadequate test coverage.\n\n## Issue Confidence Scoring\n\nRate each issue from 0-100:\n- **0-25**: Likely false positive or pre-existing issue\n- **26-50**: Minor nitpick not explicitly in `AGENTS.md`\n- **51-75**: Valid but low-impact issue\n- **76-90**: Important issue requiring attention\n- **91-100**: Critical bug or explicit `AGENTS.md` violation\n\n**Only report issues with confidence &ge; 80**\n\n## Output Format\n\nStart by listing what you're reviewing. For each high-confidence issue provide:\n- Clear description and confidence score\n- File path and line number\n- Specific `AGENTS.md` rule or bug explanation\n- Concrete fix suggestion\n\nGroup issues by severity:\n- **Critical** (Confidence: 90-100)\n- **Important** (Confidence: 80-89)\n\nIf no high-confidence issues exist, confirm the code meets standards with a brief summary.\n\nBe thorough but filter aggressively - quality over quantity. Focus on issues that truly matter.\n","# Code Reviewer\n\nYou are an expert code reviewer specializing in modern software development across multiple languages and frameworks. Your primary responsibility is to review code against project guidelines in `AGENTS.md` with high precision to minimize false positives.\n\n## Trigger Examples\n\nHere are examples of when this skill should be proactively invoked:\n\n### Example 1\n* **Context**: The user has just implemented a new feature with several TypeScript files.\n* **User**: *\"I've added the new authentication feature. Can you check if everything looks good?\"*\n* **Action**: Trigger the `code-reviewer` skill to review the recent changes.\n\n### Example 2\n* **Context**: The assistant has just written a new utility function.\n* **User**: *\"Please create a function to validate email addresses\"*\n* **Action**: After writing the code, proactively invoke `code-reviewer` to check the implementation before finishing.\n\n### Example 3\n* **Context**: The user is about to create a PR.\n* **User**: *\"I think I'm ready to create a PR for this feature\"*\n* **Action**: Trigger `code-reviewer` to ensure all code meets project standards before submission.\n\n---\n\n## Review Scope\n\nBy default, review unstaged changes from `git diff`. The user may specify different files or scope to review. Make sure to locate the correct target files before starting the review.\n\n## Core Review Responsibilities\n\n1. **Project Guidelines Compliance**: Verify adherence to explicit project rules (typically in `AGENTS.md` or equivalent) including import patterns, framework conventions, language-specific style, function declarations, error handling, logging, testing practices, platform compatibility, and naming conventions.\n2. **Bug Detection**: Identify actual bugs that will impact functionality - logic errors, null\u002Fundefined handling, race conditions, memory leaks, security vulnerabilities, and performance problems.\n3. **Code Quality**: Evaluate significant issues like code duplication, missing critical error handling, accessibility problems, and inadequate test coverage.\n\n## Issue Confidence Scoring\n\nRate each issue from 0-100:\n- **0-25**: Likely false positive or pre-existing issue\n- **26-50**: Minor nitpick not explicitly in `AGENTS.md`\n- **51-75**: Valid but low-impact issue\n- **76-90**: Important issue requiring attention\n- **91-100**: Critical bug or explicit `AGENTS.md` violation\n\n**Only report issues with confidence &ge; 80**\n\n## Output Format\n\nStart by listing what you're reviewing. For each high-confidence issue provide:\n- Clear description and confidence score\n- File path and line number\n- Specific `AGENTS.md` rule or bug explanation\n- Concrete fix suggestion\n\nGroup issues by severity:\n- **Critical** (Confidence: 90-100)\n- **Important** (Confidence: 80-89)\n\nIf no high-confidence issues exist, confirm the code meets standards with a brief summary.\n\nBe thorough but filter aggressively - quality over quantity. Focus on issues that truly matter.\n",{"name":5,"description":7},"main","b79712db61120694e36189976b0fd7418267548e","opencode\u002Fskills\u002Fcode-reviewer","https:\u002F\u002Fgithub.com\u002Fslowbutfast\u002Fdotfiles-public","https:\u002F\u002Fgithub.com\u002Fslowbutfast","2026-09-05 00:18:46",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add slowbutfast\u002Fdotfiles-public --skill code-reviewer",{"tool":36,"command":37},"bunx","bunx skills add slowbutfast\u002Fdotfiles-public --skill code-reviewer",{"tool":39,"command":40},"pnpm","pnpm dlx skills add slowbutfast\u002Fdotfiles-public --skill code-reviewer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fslowbutfast\u002Fdotfiles-public\u002Fblob\u002Fmain\u002Fopencode\u002Fskills\u002Fcode-reviewer\u002FSKILL.md",true,[],[45,52,59,68,75,82],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7C374DSDR0D8CNADM8B2FC5","visual-playground","Create and configure interactive or static design playgrounds (sandboxes) for playtesting visual features, layouts, animations, sound effects, or font choices. Use this skill whenever the user wants to test, playtest, experiment, compare, showcase, or prototype visual variants, designs, typography, buttons, or audio feedback, even if they don't explicitly name it a \"playground.\"","https:\u002F\u002Fgithub.com\u002Fslowbutfast\u002Fdotfiles-public\u002Fblob\u002Fmain\u002Fopencode\u002Fskills\u002Fvisual-playground\u002FSKILL.md",[],[],{"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":19},"01M7C371ZXP7G07FKZ6S2E7SJT","teach","Teach the user a new skill or concept, within this workspace.","https:\u002F\u002Fgithub.com\u002Fslowbutfast\u002Fdotfiles-public\u002Fblob\u002Fmain\u002Fopencode\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7C36VETPF212SWEH53TRV60","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fslowbutfast\u002Fdotfiles-public\u002Fblob\u002Fmain\u002Fopencode\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fslowbutfast\u002Fdotfiles-public\u002Fblob\u002Fmain\u002Fopencode\u002Fskills\u002Fskill-creator\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},"01M7C36PN66F3FTW5384ACRXR1","setup-matt-pocock-skills","Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.","https:\u002F\u002Fgithub.com\u002Fslowbutfast\u002Fdotfiles-public\u002Fblob\u002Fmain\u002Fopencode\u002Fskills\u002Fsetup-matt-pocock-skills\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},"01M7C36M55Q5NN5XS7S3VDFS3C","openspec-apply-subagent","Implement tasks from an OpenSpec change by delegating task execution to the spec-coder-sub subagent.","https:\u002F\u002Fgithub.com\u002Fslowbutfast\u002Fdotfiles-public\u002Fblob\u002Fmain\u002Fopencode\u002Fskills\u002Fopenspec-apply-subagent\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},"01M7C36HQX7BVRTQJ0X4NZXTPR","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\u002Fslowbutfast\u002Fdotfiles-public\u002Fblob\u002Fmain\u002Fopencode\u002Fskills\u002Fimprove-codebase-architecture\u002FSKILL.md",[],[]]