[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71EF8SJB49NMGAE3R48HN1V":3,"skill-same:01M71EF8SJB49NMGAE3R48HN1V":97},{"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":30,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":13,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":65,"install":66,"resources":78},"01M71EF8SJB49NMGAE3R48HN1V","vibe-coder-sdlc",null,"This skill should be used when users want professional SDLC practices with automated git workflows, intelligent code review, and project management without rigid processes. Orchestrates specialized agents for feature development, branch management, language-specific code review, and GitHub integration. Ideal for developers who want to stay in flow while maintaining code quality.","HuuBar\u002Fskill-routing-experiment","HuuBar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F157630575?v=4","01M71DWATRJD1XHVM5ZKB93N97","01M71DWAVGH6ENW7K4WCT2ZD0F",0,"MIT","https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fvishal\u002Fvibe-coder-sdlc\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"coder","sdlc","vibe","vibe coder sdlc","quality","github","feature development","users","python","for","code quality","manager","go","git","typescript","specialized","workflows","code review","project","branch","2026-11-10 10:12:30",false,"---\nname: vibe-coder-sdlc\ndescription: This skill should be used when users want professional SDLC practices with automated git workflows, intelligent code review, and project management without rigid processes. Orchestrates specialized agents for feature development, branch management, language-specific code review, and GitHub integration. Ideal for developers who want to stay in flow while maintaining code quality.\nlicense: MIT\nmetadata:\n  agents: orchestrator,git-workflow,code-review,project-manager\n  tech-stacks: python,typescript,javascript,go,rust,java,ruby,php\n  auto-detection: true\n---\n\n# Vibe Coder SDLC\n\nA flexible SDLC workflow system designed for developers who want professional practices without rigid processes. This skill orchestrates specialized agents to handle git workflows, code reviews, and project documentation while you stay in the zone.\n\n## Purpose\n\nThis skill provides a complete SDLC workflow that:\n- Manages feature branches and pull requests automatically\n- Reviews code with language-specific best practices\n- Tracks work in GitHub issues\n- Maintains documentation\n- Keeps you in flow without bureaucratic overhead\n\n## When to Use This Skill\n\nUse this skill when:\n- Starting a new feature or bug fix\n- Want automatic branch management and PR creation\n- Need code review before merging to main\n- Want to track work in GitHub issues automatically\n- Building projects that need documentation but don't want to write it manually\n- Working solo but want team-level quality practices\n- Want git best practices without thinking about them\n\n## Philosophy\n\n**Stay in flow, ship quality code.** This skill handles the SDLC busywork so you can focus on building. It's opinionated enough to guide you, flexible enough to not get in your way.\n\n## Core Components\n\nThis skill uses 4 specialized agents working together:\n\n1. **Orchestrator Agent** - The conductor that coordinates everything\n2. **Git Workflow Agent** - Handles branches, commits, and PRs\n3. **Code Review Agent** - Reviews your code with tech-stack awareness\n4. **Project Manager Agent** - Documents work and updates GitHub issues\n\n## How It Works\n\n### The Flow\n\n```\n1. You: \"I want to add dark mode\"\n   ↓\n2. Orchestrator: Creates plan, detects tech stack\n   ↓\n3. Git Agent: Creates feature branch 'feat\u002Fdark-mode'\n   ↓\n4. You + Claude: Build the feature\n   ↓\n5. Git Agent: Commits, pushes, creates PR\n   ↓\n6. Review Agent: Reviews code with language-specific checks\n   ↓\n7. PM Agent: Updates docs, creates\u002Fupdates GitHub issue\n   ↓\n8. Git Agent: Merges PR if review passes\n```\n\n### Tech Stack Awareness\n\n**Key Feature**: The orchestrator and review agent are tech-stack aware:\n\n- **Auto-detection**: Checks `package.json`, `requirements.txt`, `go.mod`, etc.\n- **Smart reviews**: Applies Python PEP 8 to Python, Go patterns to Go, TypeScript best practices to TS\n- **Multi-language**: Handles microservices with different languages in same PR\n- **Ask when unclear**: If detection fails, ask the user once\n- **Remember for session**: Store tech stack info to avoid repeated questions\n\n## Workflow Phases\n\n### 1. Plan Phase\n- Understand what needs to be built\n- Break it down into steps\n- Create a todo list\n- Detect or ask about tech stack (if not already known)\n\n### 2. Setup Phase\n- Use git-workflow-agent to create feature branch\n- Branch name format: `feat\u002F`, `fix\u002F`, `refactor\u002F`, `docs\u002F`\n\n### 3. Development Phase\n- Help user build the feature\n- Make commits with clear messages\n- Keep the user in flow - don't over-document\n\n### 4. Review Phase\n- Use git-workflow-agent to push and create PR\n- Use code-review-agent to review the code\n  - Agent detects tech stack from repo\u002FPR\n  - Applies language-specific best practices\n- If issues found: fix them before merge\n- Add review comments to the PR\n\n### 5. Documentation Phase\n- Use project-manager-agent to:\n  - Create\u002Fupdate GitHub issue tracking this work\n  - Update relevant documentation\n  - Add summary comments to PR\n\n### 6. Merge Phase\n- If review passes: use git-workflow-agent to merge\n- Delete feature branch\n- Celebrate! 🎉\n\n## Agent Setup\n\nTo use this skill, set up the 4 agents in your project's `.claude\u002Fagents\u002F` directory:\n\n### Required Agents\n\n1. **sdlc-orchestrator** - See [Orchestrator Agent Guide](references\u002Forchestrator-agent.md)\n2. **git-workflow-agent** - See [Git Workflow Agent Guide](references\u002Fgit-workflow-agent.md)\n3. **code-review-agent** - See [Code Review Agent Guide](references\u002Fcode-review-agent.md)\n4. **project-manager-agent** - See [Project Manager Agent Guide](references\u002Fproject-manager-agent.md)\n\nEach reference guide contains the complete agent definition ready to copy into your `.claude\u002Fagents\u002F` directory.\n\n## Quick Start\n\n### Step 1: Copy Agent Files\n\n```bash\n# In your project root\nmkdir -p .claude\u002Fagents\n\n# Copy the 4 agent definitions from this skill's references\u002F folder\n# to your project's .claude\u002Fagents\u002F folder\n```\n\n### Step 2: Install GitHub CLI\n\n```bash\n# macOS\nbrew install gh\n\n# Linux\nsudo apt install gh\n\n# Windows\nwinget install GitHub.cli\n\n# Authenticate\ngh auth login\n```\n\n### Step 3: Start Using\n\n```\n\"Hey Claude, let's use the vibe-coder-sdlc skill to add [feature]\"\n```\n\nThe agents handle the process, you handle the code.\n\n## Usage Examples\n\n### Example 1: Simple Feature Addition\n\n**User**: \"Add a search bar to the homepage\"\n\n**Workflow**:\n1. Git Agent: Create branch 'feat\u002Fhomepage-search'\n2. [User builds the feature]\n3. Git Agent: Commit and push, create PR\n4. Review Agent: Review code (approved)\n5. PM Agent: Create issue #45, update README, update CHANGELOG\n6. Git Agent: Merge PR, close issue\n\n### Example 2: Bug Fix\n\n**User**: \"Login form not working on mobile\"\n\n**Workflow**:\n1. Git Agent: Create branch 'fix\u002Fmobile-login'\n2. [User fixes the bug]\n3. Git Agent: Commit and push, create PR\n4. Review Agent: Review code (request changes - missing test)\n5. [User adds test]\n6. Review Agent: Re-review (approved)\n7. PM Agent: Create issue #46, add PR description\n8. Git Agent: Merge PR, close issue\n\n### Example 3: Multi-Language Project (Microservices)\n\n**User**: \"Add a new API endpoint in the Go service and update the TypeScript frontend to use it\"\n\n**Workflow**:\n1. Git Agent: Create branch 'feat\u002Fnew-api-endpoint'\n2. [User builds Go API endpoint]\n3. Review Agent: Detects Go, applies Go-specific checks\n4. [User updates TypeScript frontend]\n5. Review Agent: Detects TypeScript, applies TS-specific checks\n6. Git Agent: Create PR\n7. Review Agent: Reviews both Go and TypeScript changes\n8. PM Agent: Updates docs for both services\n9. Git Agent: Merge PR\n\n### Example 4: First Time in a New Repo\n\n**User**: \"Add dark mode to the app\"\n\n**Workflow**:\n1. Orchestrator detects tech stack:\n   - Finds package.json → Node.js\u002FTypeScript\n   - Finds next.config.js → Next.js detected\n   - Stores: \"TypeScript + Next.js + React\"\n2. Git Agent: Create branch 'feat\u002Fdark-mode'\n3. [User builds dark mode]\n4. Review Agent: Uses TypeScript + React checklist\n5. Git Agent: Create PR\n6. PM Agent: Updates README with dark mode info\n7. Git Agent: Merge PR\n\n## Configuration\n\n### Customize for Your Workflow\n\nCreate `.claude\u002Fsdlc-config.json`:\n\n```json\n{\n  \"branchNaming\": {\n    \"feature\": \"feat\u002F\",\n    \"bugfix\": \"fix\u002F\",\n    \"refactor\": \"refactor\u002F\",\n    \"docs\": \"docs\u002F\"\n  },\n  \"commitConvention\": \"conventional\",\n  \"reviewRequired\": true,\n  \"autoMerge\": false,\n  \"documentation\": {\n    \"updateChangelog\": true,\n    \"updateReadme\": true,\n    \"requireTests\": true\n  },\n  \"github\": {\n    \"createIssues\": true,\n    \"linkPRsToIssues\": true,\n    \"addLabels\": true\n  }\n}\n```\n\n## Supported Tech Stacks\n\nThe code review agent automatically detects and applies best practices for:\n\n- **Python**: PEP 8, type hints, context managers\n- **TypeScript\u002FJavaScript**: ESLint, proper types, async patterns\n- **Go**: Error handling, context usage, goroutine management\n- **Rust**: Ownership, clippy lints, error handling\n- **Java**: Exception handling, streams, null safety\n- **Ruby**: RuboCop, ActiveRecord patterns\n- **PHP**: PSR standards, prepared statements\n\nSee [Code Review Agent Guide](references\u002Fcode-review-agent.md) for complete language-specific checklists.\n\n## Best Practices\n\n### 1. Keep PRs Small\n- Easier to review\n- Faster to merge\n- Less risky\n\n**Good**: \"Add user avatar display\"\n**Bad**: \"Redesign entire user profile system\"\n\n### 2. Write Commits for Future You\nSix months from now, you'll want to know WHY you made changes.\n\n**Good**: `fix(auth): handle expired tokens by redirecting to login`\n**Bad**: `fix bug`\n\n### 3. Review Your Own Code First\nBefore the review agent runs, do a self-review:\n```bash\ngh pr diff \u003Cnumber>\n```\n\n### 4. Document As You Go\nDon't leave documentation for \"later.\" Update docs in the same PR.\n\n### 5. Use Labels Effectively\n```\npriority: high\u002Fmedium\u002Flow\ntype: bug\u002Ffeature\u002Frefactor\nstatus: in-progress\u002Freview\u002Fblocked\narea: frontend\u002Fbackend\u002Fdb\n```\n\n### 6. Link Everything\n- PR mentions issue: \"Closes #123\"\n- Commits reference issues: \"feat: add search (ref #123)\"\n- Issues reference PRs: \"Implemented in PR #456\"\n\n## Troubleshooting\n\n### \"Agent not responding\"\nCheck that agent files exist in `.claude\u002Fagents\u002F`\n\n### \"gh command not found\"\nInstall GitHub CLI (see Quick Start)\n\n### \"Can't create PR\"\nMake sure you're authenticated:\n```bash\ngh auth status\ngh auth login\n```\n\n### \"Review agent too strict\"\nAdjust review agent instructions to match your needs. It's your workflow!\n\n### \"Too much overhead\"\nSkip steps that don't add value:\n- Turn off auto-issue creation\n- Skip changelog for small changes\n- Disable review for docs-only changes\n\n## Advanced Usage\n\n### CI\u002FCD Integration\n\nAdd to your `.github\u002Fworkflows\u002Fpr-check.yml`:\n\n```yaml\nname: PR Checks\non: [pull_request]\n\njobs:\n  review:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v3\n      - name: Run tests\n        run: npm test\n      - name: Run linter\n        run: npm run lint\n```\n\n### Custom Review Rules\n\nExtend the review agent for your stack. See [Code Review Agent Guide](references\u002Fcode-review-agent.md) for customization examples.\n\n### Team Workflows\n\nFor teams, add these practices:\n- Require PR approvals from teammates\n- Add CODEOWNERS file\n- Use branch protection rules\n- Set up required status checks\n\n## Philosophy Recap\n\nThis skill is built on these principles:\n\n1. **Quality without bureaucracy** - Professional practices, minimal overhead\n2. **Automation over documentation** - Let agents handle busywork\n3. **Flexibility over rigidity** - Adapt to your style\n4. **Flow over process** - Don't interrupt creative work\n5. **Ship over perfect** - Done and good beats perfect and never\n\n## Next Steps\n\nOnce you've used this skill:\n\n1. **Customize the agents** - Make them match your workflow\n2. **Add your own agents** - Create specialized agents for your stack\n3. **Share with your team** - Adapt for team workflows\n4. **Iterate** - This is a starting point, make it yours\n\n---\n\n**Built for vibe coders who want to ship quality code without the SDLC headaches.**\n","# Vibe Coder SDLC\n\nA flexible SDLC workflow system designed for developers who want professional practices without rigid processes. This skill orchestrates specialized agents to handle git workflows, code reviews, and project documentation while you stay in the zone.\n\n## Purpose\n\nThis skill provides a complete SDLC workflow that:\n- Manages feature branches and pull requests automatically\n- Reviews code with language-specific best practices\n- Tracks work in GitHub issues\n- Maintains documentation\n- Keeps you in flow without bureaucratic overhead\n\n## When to Use This Skill\n\nUse this skill when:\n- Starting a new feature or bug fix\n- Want automatic branch management and PR creation\n- Need code review before merging to main\n- Want to track work in GitHub issues automatically\n- Building projects that need documentation but don't want to write it manually\n- Working solo but want team-level quality practices\n- Want git best practices without thinking about them\n\n## Philosophy\n\n**Stay in flow, ship quality code.** This skill handles the SDLC busywork so you can focus on building. It's opinionated enough to guide you, flexible enough to not get in your way.\n\n## Core Components\n\nThis skill uses 4 specialized agents working together:\n\n1. **Orchestrator Agent** - The conductor that coordinates everything\n2. **Git Workflow Agent** - Handles branches, commits, and PRs\n3. **Code Review Agent** - Reviews your code with tech-stack awareness\n4. **Project Manager Agent** - Documents work and updates GitHub issues\n\n## How It Works\n\n### The Flow\n\n```\n1. You: \"I want to add dark mode\"\n   ↓\n2. Orchestrator: Creates plan, detects tech stack\n   ↓\n3. Git Agent: Creates feature branch 'feat\u002Fdark-mode'\n   ↓\n4. You + Claude: Build the feature\n   ↓\n5. Git Agent: Commits, pushes, creates PR\n   ↓\n6. Review Agent: Reviews code with language-specific checks\n   ↓\n7. PM Agent: Updates docs, creates\u002Fupdates GitHub issue\n   ↓\n8. Git Agent: Merges PR if review passes\n```\n\n### Tech Stack Awareness\n\n**Key Feature**: The orchestrator and review agent are tech-stack aware:\n\n- **Auto-detection**: Checks `package.json`, `requirements.txt`, `go.mod`, etc.\n- **Smart reviews**: Applies Python PEP 8 to Python, Go patterns to Go, TypeScript best practices to TS\n- **Multi-language**: Handles microservices with different languages in same PR\n- **Ask when unclear**: If detection fails, ask the user once\n- **Remember for session**: Store tech stack info to avoid repeated questions\n\n## Workflow Phases\n\n### 1. Plan Phase\n- Understand what needs to be built\n- Break it down into steps\n- Create a todo list\n- Detect or ask about tech stack (if not already known)\n\n### 2. Setup Phase\n- Use git-workflow-agent to create feature branch\n- Branch name format: `feat\u002F`, `fix\u002F`, `refactor\u002F`, `docs\u002F`\n\n### 3. Development Phase\n- Help user build the feature\n- Make commits with clear messages\n- Keep the user in flow - don't over-document\n\n### 4. Review Phase\n- Use git-workflow-agent to push and create PR\n- Use code-review-agent to review the code\n  - Agent detects tech stack from repo\u002FPR\n  - Applies language-specific best practices\n- If issues found: fix them before merge\n- Add review comments to the PR\n\n### 5. Documentation Phase\n- Use project-manager-agent to:\n  - Create\u002Fupdate GitHub issue tracking this work\n  - Update relevant documentation\n  - Add summary comments to PR\n\n### 6. Merge Phase\n- If review passes: use git-workflow-agent to merge\n- Delete feature branch\n- Celebrate! 🎉\n\n## Agent Setup\n\nTo use this skill, set up the 4 agents in your project's `.claude\u002Fagents\u002F` directory:\n\n### Required Agents\n\n1. **sdlc-orchestrator** - See [Orchestrator Agent Guide](references\u002Forchestrator-agent.md)\n2. **git-workflow-agent** - See [Git Workflow Agent Guide](references\u002Fgit-workflow-agent.md)\n3. **code-review-agent** - See [Code Review Agent Guide](references\u002Fcode-review-agent.md)\n4. **project-manager-agent** - See [Project Manager Agent Guide](references\u002Fproject-manager-agent.md)\n\nEach reference guide contains the complete agent definition ready to copy into your `.claude\u002Fagents\u002F` directory.\n\n## Quick Start\n\n### Step 1: Copy Agent Files\n\n```bash\n# In your project root\nmkdir -p .claude\u002Fagents\n\n# Copy the 4 agent definitions from this skill's references\u002F folder\n# to your project's .claude\u002Fagents\u002F folder\n```\n\n### Step 2: Install GitHub CLI\n\n```bash\n# macOS\nbrew install gh\n\n# Linux\nsudo apt install gh\n\n# Windows\nwinget install GitHub.cli\n\n# Authenticate\ngh auth login\n```\n\n### Step 3: Start Using\n\n```\n\"Hey Claude, let's use the vibe-coder-sdlc skill to add [feature]\"\n```\n\nThe agents handle the process, you handle the code.\n\n## Usage Examples\n\n### Example 1: Simple Feature Addition\n\n**User**: \"Add a search bar to the homepage\"\n\n**Workflow**:\n1. Git Agent: Create branch 'feat\u002Fhomepage-search'\n2. [User builds the feature]\n3. Git Agent: Commit and push, create PR\n4. Review Agent: Review code (approved)\n5. PM Agent: Create issue #45, update README, update CHANGELOG\n6. Git Agent: Merge PR, close issue\n\n### Example 2: Bug Fix\n\n**User**: \"Login form not working on mobile\"\n\n**Workflow**:\n1. Git Agent: Create branch 'fix\u002Fmobile-login'\n2. [User fixes the bug]\n3. Git Agent: Commit and push, create PR\n4. Review Agent: Review code (request changes - missing test)\n5. [User adds test]\n6. Review Agent: Re-review (approved)\n7. PM Agent: Create issue #46, add PR description\n8. Git Agent: Merge PR, close issue\n\n### Example 3: Multi-Language Project (Microservices)\n\n**User**: \"Add a new API endpoint in the Go service and update the TypeScript frontend to use it\"\n\n**Workflow**:\n1. Git Agent: Create branch 'feat\u002Fnew-api-endpoint'\n2. [User builds Go API endpoint]\n3. Review Agent: Detects Go, applies Go-specific checks\n4. [User updates TypeScript frontend]\n5. Review Agent: Detects TypeScript, applies TS-specific checks\n6. Git Agent: Create PR\n7. Review Agent: Reviews both Go and TypeScript changes\n8. PM Agent: Updates docs for both services\n9. Git Agent: Merge PR\n\n### Example 4: First Time in a New Repo\n\n**User**: \"Add dark mode to the app\"\n\n**Workflow**:\n1. Orchestrator detects tech stack:\n   - Finds package.json → Node.js\u002FTypeScript\n   - Finds next.config.js → Next.js detected\n   - Stores: \"TypeScript + Next.js + React\"\n2. Git Agent: Create branch 'feat\u002Fdark-mode'\n3. [User builds dark mode]\n4. Review Agent: Uses TypeScript + React checklist\n5. Git Agent: Create PR\n6. PM Agent: Updates README with dark mode info\n7. Git Agent: Merge PR\n\n## Configuration\n\n### Customize for Your Workflow\n\nCreate `.claude\u002Fsdlc-config.json`:\n\n```json\n{\n  \"branchNaming\": {\n    \"feature\": \"feat\u002F\",\n    \"bugfix\": \"fix\u002F\",\n    \"refactor\": \"refactor\u002F\",\n    \"docs\": \"docs\u002F\"\n  },\n  \"commitConvention\": \"conventional\",\n  \"reviewRequired\": true,\n  \"autoMerge\": false,\n  \"documentation\": {\n    \"updateChangelog\": true,\n    \"updateReadme\": true,\n    \"requireTests\": true\n  },\n  \"github\": {\n    \"createIssues\": true,\n    \"linkPRsToIssues\": true,\n    \"addLabels\": true\n  }\n}\n```\n\n## Supported Tech Stacks\n\nThe code review agent automatically detects and applies best practices for:\n\n- **Python**: PEP 8, type hints, context managers\n- **TypeScript\u002FJavaScript**: ESLint, proper types, async patterns\n- **Go**: Error handling, context usage, goroutine management\n- **Rust**: Ownership, clippy lints, error handling\n- **Java**: Exception handling, streams, null safety\n- **Ruby**: RuboCop, ActiveRecord patterns\n- **PHP**: PSR standards, prepared statements\n\nSee [Code Review Agent Guide](references\u002Fcode-review-agent.md) for complete language-specific checklists.\n\n## Best Practices\n\n### 1. Keep PRs Small\n- Easier to review\n- Faster to merge\n- Less risky\n\n**Good**: \"Add user avatar display\"\n**Bad**: \"Redesign entire user profile system\"\n\n### 2. Write Commits for Future You\nSix months from now, you'll want to know WHY you made changes.\n\n**Good**: `fix(auth): handle expired tokens by redirecting to login`\n**Bad**: `fix bug`\n\n### 3. Review Your Own Code First\nBefore the review agent runs, do a self-review:\n```bash\ngh pr diff \u003Cnumber>\n```\n\n### 4. Document As You Go\nDon't leave documentation for \"later.\" Update docs in the same PR.\n\n### 5. Use Labels Effectively\n```\npriority: high\u002Fmedium\u002Flow\ntype: bug\u002Ffeature\u002Frefactor\nstatus: in-progress\u002Freview\u002Fblocked\narea: frontend\u002Fbackend\u002Fdb\n```\n\n### 6. Link Everything\n- PR mentions issue: \"Closes #123\"\n- Commits reference issues: \"feat: add search (ref #123)\"\n- Issues reference PRs: \"Implemented in PR #456\"\n\n## Troubleshooting\n\n### \"Agent not responding\"\nCheck that agent files exist in `.claude\u002Fagents\u002F`\n\n### \"gh command not found\"\nInstall GitHub CLI (see Quick Start)\n\n### \"Can't create PR\"\nMake sure you're authenticated:\n```bash\ngh auth status\ngh auth login\n```\n\n### \"Review agent too strict\"\nAdjust review agent instructions to match your needs. It's your workflow!\n\n### \"Too much overhead\"\nSkip steps that don't add value:\n- Turn off auto-issue creation\n- Skip changelog for small changes\n- Disable review for docs-only changes\n\n## Advanced Usage\n\n### CI\u002FCD Integration\n\nAdd to your `.github\u002Fworkflows\u002Fpr-check.yml`:\n\n```yaml\nname: PR Checks\non: [pull_request]\n\njobs:\n  review:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v3\n      - name: Run tests\n        run: npm test\n      - name: Run linter\n        run: npm run lint\n```\n\n### Custom Review Rules\n\nExtend the review agent for your stack. See [Code Review Agent Guide](references\u002Fcode-review-agent.md) for customization examples.\n\n### Team Workflows\n\nFor teams, add these practices:\n- Require PR approvals from teammates\n- Add CODEOWNERS file\n- Use branch protection rules\n- Set up required status checks\n\n## Philosophy Recap\n\nThis skill is built on these principles:\n\n1. **Quality without bureaucracy** - Professional practices, minimal overhead\n2. **Automation over documentation** - Let agents handle busywork\n3. **Flexibility over rigidity** - Adapt to your style\n4. **Flow over process** - Don't interrupt creative work\n5. **Ship over perfect** - Done and good beats perfect and never\n\n## Next Steps\n\nOnce you've used this skill:\n\n1. **Customize the agents** - Make them match your workflow\n2. **Add your own agents** - Create specialized agents for your stack\n3. **Share with your team** - Adapt for team workflows\n4. **Iterate** - This is a starting point, make it yours\n\n---\n\n**Built for vibe coders who want to ship quality code without the SDLC headaches.**\n",{"name":5,"license":14,"metadata":56,"description":7},{"agents":57,"tech-stacks":58,"auto-detection":59},"orchestrator,git-workflow,code-review,project-manager","python,typescript,javascript,go,rust,java,ruby,php",true,"main","0731f842467bc34c43e7ca68860c1903da2c4b5a","unified_skills\u002Fvishal\u002Fvibe-coder-sdlc","https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment","https:\u002F\u002Fgithub.com\u002FHuuBar","2026-04-22 07:49:44",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":59},[68,71,74],{"tool":69,"command":70},"npx","npx skills add HuuBar\u002Fskill-routing-experiment --skill vibe-coder-sdlc",{"tool":72,"command":73},"bunx","bunx skills add HuuBar\u002Fskill-routing-experiment --skill vibe-coder-sdlc",{"tool":75,"command":76},"pnpm","pnpm dlx skills add HuuBar\u002Fskill-routing-experiment --skill vibe-coder-sdlc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fvishal\u002Fvibe-coder-sdlc\u002FSKILL.md",[79,85,89,93],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fcode-review-agent.md","REFERENCE","参考文档",8487,"https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fvishal\u002Fvibe-coder-sdlc\u002Freferences\u002Fcode-review-agent.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fgit-workflow-agent.md",2554,"https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fvishal\u002Fvibe-coder-sdlc\u002Freferences\u002Fgit-workflow-agent.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Forchestrator-agent.md",2955,"https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fvishal\u002Fvibe-coder-sdlc\u002Freferences\u002Forchestrator-agent.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fproject-manager-agent.md",4018,"https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fvishal\u002Fvibe-coder-sdlc\u002Freferences\u002Fproject-manager-agent.md",[98,128,152,176,204,236],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":107,"publishedAt":51},"01M71EF4DQE82S6YB7KAGTGNY8","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fvishal\u002Fvercel-react-best-practices\u002FSKILL.md",[104],{"categoryNo":105,"categoryName":106,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127],"react","react best practices","vercel react best practices","vercel","best practices","performance","writing","when","code","tasks","components","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":132,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":137,"publishedAt":51},"01M71EEG5EBH2VH21XQME9GXQT","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fvishal\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fvishal\u002Fskill-creator\u002FSKILL.md",[136],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[138,139,140,141,47,115,46,142,143,144,145,146,147,148,40,149,150,38,151],"skill creator","creator","knowledge","new","capabilities","create","update","new skill","guide","existing skill","integrations","tool","Existing","with",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":159,"publishedAt":51},"01M71EE01V09M43697X6SJ2YFZ","readme-generator","This skill creates or updates a README.md file in the GitHub home directory of the current project. The README.md file it generates will conform to GitHub best practices, including badges, project overview, site metrics, getting started instructions, and comprehensive documentation.","https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fvishal\u002Freadme-generator\u002FSKILL.md",[158],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[160,161,162,163,49,164,165,166,167,168,169,170,112,171,172,36,173,174,175],"README","generator","readme generator","getting started","updates","project overview","documentation","conform","directory","metrics","overview","file","home","instructions","site","it",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":186,"publishedAt":51},"01M71EDVK53D97Q5AG6KPQHWFX","quiz-generator","This skill generates interactive multiple-choice quizzes for each chapter of an intelligent textbook, with questions aligned to specific concepts from the learning graph and distributed across Bloom's Taxonomy cognitive levels to assess student understanding effectively. Use this skill after chapter content has been written and the learning graph exists.","https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fvishal\u002Fquiz-generator\u002FSKILL.md",[182,183],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":184,"categoryName":185,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000039","教师与教育",[187,188,161,189,190,191,192,193,194,195,40,196,197,198,199,200,201,151,202,203],"quiz generator","quiz","bloom","choice","chapter","student","across","concepts","graph","learning","assess","taxonomy","use","distributed","interactive","multiple-choice","questions",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":208,"sourceHtmlUrl":209,"categories":210,"keywords":220,"publishedAt":51},"01M71EDRYN945162ESNGE95M1N","paper-writing","Expert guidance for writing high-quality academic and research papers. Use when the user wants to write, structure, revise, or improve academic papers, research articles, conference papers, or technical reports. Provides comprehensive support for all stages from planning to final polish.","https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fvishal\u002Fpaper-writing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fvishal\u002Fpaper-writing\u002FSKILL.md",[211,214,217],{"categoryNo":212,"categoryName":213,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":215,"categoryName":216,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":218,"categoryName":219,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000036","内容创作者",[221,114,222,223,224,225,226,115,116,227,228,229,230,231,232,233,40,234,199,235],"Paper Writing","paper","community","papers","expert","improve","reports","structure","support","write","polish","revise","planning","technical","research",{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":243,"publishedAt":51},"01M71ECJX9VQK2M6MBYF0FQNKJ","linkedin-announcement-generator","This skill generates professional LinkedIn announcement text for intelligent textbooks by analyzing book metrics, chapter content, and learning resources to create engaging posts with key statistics, hashtags, and links to the published site. Use this skill when you need to create social media announcements about textbook completion or major milestones.","https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fvishal\u002Flinkedin-announcement-generator\u002FSKILL.md",[242],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[244,245,246,161,247,248,249,250,251,191,252,115,253,254,255,143,256,169,257,40],"announcement","linkedin announcement generator","linkedin","posts","Media","resources","professional","social","milestones","you","statistics","text","analyzing","links"]