[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DF5R1XHQ8FBT0BKZBFDR9J":3,"skill-same:01M6DF5R1XHQ8FBT0BKZBFDR9J":68},{"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":26,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":14,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6DF5R1XHQ8FBT0BKZBFDR9J","create-issue",null,"Create comprehensive GitHub issues with TDD plans, acceptance criteria, and agent instructions for autonomous PR lifecycle management","Prekzursil\u002Fagent-skills-toolchain","Prekzursil","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54636077?v=4","01M6DACZ1PCQHD99SCR1YXG28B","Andrei Mihai Visalon","01M6DACZ670WZF535V3WYYSS4Z",0,"MIT","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fcreate-issue\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"create","issue","create issue","github","tdd","pr lifecycle","pr","github issues","issues","acceptance","lifecycle","instructions","management","autonomous","acceptance criteria","plans","2026-11-10 10:12:30",false,"---\nname: create-issue\ndescription: Create comprehensive GitHub issues with TDD plans, acceptance criteria, and agent instructions for autonomous PR lifecycle management\n---\n\n# Create GitHub Issue Skill\n\nCreate comprehensive, well-structured GitHub issues with embedded agent instructions for autonomous PR lifecycle management.\n\n## Overview\n\nThis skill generates GitHub issues that are self-contained work packets. Each issue includes:\n\n1. **Problem\u002FFeature specification** with clear scope\n2. **Technical specification** with types, schemas, and API design\n3. **TDD Implementation Plan** with test-first cycles\n4. **Acceptance Criteria** checklist\n5. **Agent Instructions** for complete PR lifecycle (implementation → review → merge)\n\n## Usage\n\n```\n\u002Fcreate-issue\n```\n\n## Interactive Flow\n\n### Step 1: Issue Type\n\nAsk the user:\n\n```\nWhat type of issue is this?\n1. Feature - New functionality\n2. Bug - Something broken\n3. Refactor - Improving existing code\n```\n\n### Step 2: Brief Description\n\n```\nBrief description of the problem or feature? (1-2 sentences)\n```\n\n### Step 3: Complexity Assessment\n\n```\nWhat's the estimated complexity?\n1. Simple (\u003C 1 day)\n2. Medium (2-5 days)\n3. Complex (> 1 week)\n```\n\n### Step 4: Context Gathering\n\n```\nAny related files, services, or issues I should reference?\n(Or say \"explore codebase\" and I'll investigate)\n```\n\n### Step 5: Generate Issue\n\nBased on inputs, generate the full issue using the appropriate template below.\n\n---\n\n## Issue Templates\n\n### Feature Template\n\n````markdown\n## Summary\n\n[1-2 sentence description]\n\n**Complexity**: [simple|medium|complex]\n**Estimated Effort**: [X days]\n\n---\n\n## Problem\n\n[What problem does this solve? Why is it needed?]\n\n### Evidence\n\n[Logs, metrics, user reports, or reasoning]\n\n### Scope\n\n- IN SCOPE: [what's included]\n- OUT OF SCOPE: [what's explicitly NOT included]\n\n---\n\n## Architecture Decision\n\n**Decision**: [What approach will be taken]\n**Rationale**: [Why this approach, why NOT alternatives]\n\n---\n\n## Technical Specification\n\n### Types\u002FInterfaces\n\n```typescript\n\u002F\u002F Key type definitions\n```\n````\n\n### Zod Schemas (if applicable)\n\n```typescript\n\u002F\u002F Validation schemas\n```\n\n### API Endpoints (if applicable)\n\n| Method | Path | Description |\n| ------ | ---- | ----------- |\n\n### Database Changes (if applicable)\n\n[Schema changes, migrations needed]\n\n---\n\n## TDD Implementation Plan\n\n### Cycle 1: [Happy Path]\n\n```typescript\nit(\"should [expected behavior]\", async () => {\n  \u002F\u002F Test code\n});\n```\n\n### Cycle 2: [Error Handling]\n\n```typescript\nit(\"should handle [error case]\", async () => {\n  \u002F\u002F Test code\n});\n```\n\n### Cycle 3: [Edge Cases]\n\n### Cycle 4: [Integration]\n\n---\n\n## Error Handling\n\n| Scenario | Behavior | Logging |\n| -------- | -------- | ------- |\n\n---\n\n## Implementation Phases\n\n### Phase 1: [Core] (High Priority)\n\n- [ ] Task 1\n- [ ] Task 2\n\n### Phase 2: [Enhancement] (Medium Priority)\n\n- [ ] Task 3\n\n---\n\n## Files to Create\u002FModify\n\n- **NEW**: `path\u002Fto\u002Fnew\u002Ffile.ts`\n- `path\u002Fto\u002Fexisting\u002Ffile.ts` - [what changes]\n\n---\n\n## Acceptance Criteria\n\n- [ ] All TDD cycles implemented with passing tests\n- [ ] Zero TypeScript errors (`pnpm typecheck`)\n- [ ] Zero lint warnings (`pnpm lint`)\n- [ ] All tests pass (`pnpm test --run`)\n- [ ] **JSDoc documentation** added to all new\u002Fmodified services\n- [ ] **`docs\u002FSERVICE_INVENTORY.md`** updated (if new\u002Fmodified service)\n- [ ] **Mock factories** added\u002Fupdated (if new service)\n- [ ] PR created and all CI checks pass\n- [ ] **ALL code review comments addressed** (see Agent Instructions)\n- [ ] All review threads resolved\n- [ ] PR approved and merged\n\n---\n\n## Agent Instructions\n\n**CRITICAL**: Follow this protocol when implementing this issue. A PR is NOT complete until ALL steps are done.\n\n### Phase 0: Research (BEFORE writing any code)\n\n**Read these files first to avoid reinventing the wheel:**\n\n1. **Service Inventory** - Check for existing services that might already do what you need:\n\n   ```bash\n   # Read the service inventory\n   cat docs\u002FSERVICE_INVENTORY.md\n   # Or search for specific functionality\n   grep -i \"embedding\\|search\\|cache\" docs\u002FSERVICE_INVENTORY.md\n   ```\n\n2. **Mock Factories** - Review existing mocks to reuse patterns:\n\n   ```bash\n   ls src\u002Ftest-utils\u002Ffactories\u002F\n   ```\n\n3. **Similar Services** - Find services with similar patterns:\n   ```bash\n   # Find orchestrator patterns\n   ls src\u002Flib\u002Fservices\u002F*-orchestrator*.ts\n   # Find persistence patterns\n   ls src\u002Flib\u002Fservices\u002F*-persistence*.ts\n   ```\n\n**Why this matters**: Reusing existing services and patterns saves time, maintains consistency, and prevents duplicate code.\n\n### Phase A: Implementation\n\n1. Create feature branch from main: `git checkout -b feat\u002F[short-name]`\n2. Follow TDD cycles exactly as specified above\n3. **Add JSDoc documentation** to all new\u002Fmodified services\n4. Run local validation: `pnpm lint && pnpm typecheck && pnpm test --run`\n5. **Update service inventory** (if new service)\n6. Create PR with comprehensive description using `\u002Fcreate-pr`\n\n### Phase B: Code Review Iteration\n\n**Wait for code reviews before proceeding. Do NOT mark complete after pushing code.**\n\nFor EACH code review iteration:\n\n1. **Fetch ALL comments** (including trivial, nitpicks, and out-of-scope):\n\n   ```bash\n   PR_NUMBER=XXX\n   OWNER=$(gh repo view --json owner -q .owner.login)\n   REPO=$(gh repo view --json name -q .name)\n   gh api \"repos\u002F$OWNER\u002F$REPO\u002Fpulls\u002F$PR_NUMBER\u002Fcomments\" --paginate\n   ```\n\n2. **Address ALL comments by category**:\n\n   | Type                   | Action                                               |\n   | ---------------------- | ---------------------------------------------------- |\n   | Critical\u002FMajor         | Fix immediately                                      |\n   | Medium\u002FMinor           | Fix before merge                                     |\n   | **Trivial\u002FNitpick**    | **Fix these too!** Do NOT skip                       |\n   | **Out-of-scope**       | **Investigate thoroughly** - often the BEST insights |\n\n3. **For each comment**:\n   - **\u003C 1 day of work** → Implement the fix in this PR\n   - **> 1 day OR architectural** → Create a new GitHub issue, link in response\n   - **Disagree** → Reply explaining why with technical reasoning\n\n4. **After making changes**:\n\n   ```bash\n   pnpm lint && pnpm typecheck && pnpm test --run\n   git add . && git commit -m \"fix: address review feedback\" && git push\n   ```\n\n5. **Respond to EVERY comment thread individually**:\n\n   ```bash\n   COMMENT_ID=XXX\n   CURRENT_USER=$(gh api user -q '.login')\n   gh api \"\u002Frepos\u002F$OWNER\u002F$REPO\u002Fpulls\u002F$PR_NUMBER\u002Fcomments\u002F$COMMENT_ID\u002Freplies\" \\\n     -X POST \\\n     -f body=\"Fixed in commit $(git rev-parse --short HEAD). [explanation]\n\n   *(Response by Claude on behalf of @$CURRENT_USER)*\"\n   ```\n\n6. **Wait for next review cycle** - Do NOT resolve threads yourself\n\n7. **Repeat steps 1-6** until reviewer confirms satisfaction\n\n### Phase C: Thread Resolution\n\nOnly AFTER reviewer approval:\n\n1. Re-fetch all threads to get current IDs\n2. Resolve each thread:\n\n   ```bash\n   THREAD_ID=\"PRRT_xxx\"\n   gh api graphql -f threadId=\"$THREAD_ID\" -f query='\n     mutation($threadId: ID!) {\n       resolveReviewThread(input: {threadId: $threadId}) {\n         thread { id isResolved }\n       }\n     }'\n   ```\n\n3. Verify all threads resolved before proceeding\n\n### Phase D: Merge Readiness\n\nPR is ready for merge ONLY when ALL are true:\n\n- [ ] All CI checks pass (green)\n- [ ] **EVERY** code review comment addressed (including trivial\u002Fout-of-scope)\n- [ ] **EVERY** thread has individual response\n- [ ] All threads are resolved (after reviewer approval)\n- [ ] GitHub issues created for any deferred work (> 1 day)\n- [ ] No pending reviewer comments awaiting response\n\n### Phase E: Squash Merge and Cleanup\n\n**IMPORTANT**: Always use squash merge, never regular merge.\n\n1. **Squash and merge** the PR (combines all commits into one clean commit):\n\n   ```bash\n   # Via GitHub CLI\n   gh pr merge $PR_NUMBER --squash --delete-branch\n\n   # Or via GitHub web UI:\n   # Click \"Squash and merge\" (NOT \"Merge\" or \"Rebase and merge\")\n   ```\n\n2. **Delete the feature branch** (automatically done with --delete-branch flag):\n\n   ```bash\n   # If branch wasn't auto-deleted:\n   git push origin --delete feat\u002F[branch-name]\n   git branch -d feat\u002F[branch-name]\n   ```\n\n3. **Update local main**:\n\n   ```bash\n   git checkout main\n   git pull origin main\n   ```\n\n### Reference\n\nSee the `\u002Fmetaswarm:handle-pr-comments` command for detailed protocol.\n\n---\n\n## Related Issues\n\n- [Link to related issues]\n\n## References\n\n- [Link to relevant docs, specs, or PRs]\n\n````\n\n---\n\n### Bug Template\n\nUse the Feature template with these modifications:\n\n**Title format**: `fix: [brief description]`\n\n**Replace \"Problem\" section with**:\n\n```markdown\n## Bug Report\n\n**Priority**: [P0-Critical|P1-High|P2-Medium|P3-Low]\n**Affected Users**: [scope of impact]\n**First Reported**: [date\u002Fsource]\n\n### Expected Behavior\n\n[What should happen]\n\n### Actual Behavior\n\n[What actually happens]\n\n### Steps to Reproduce\n\n1. Step 1\n2. Step 2\n3. Step 3\n\n### Root Cause Analysis\n\n[If known, explain why this is happening]\n\n### Evidence\n\n[Logs, stack traces, screenshots]\n````\n\n**Replace \"TDD Implementation Plan\" with**:\n\n````markdown\n## Test Cases\n\n### Test 1: Verify fix for reported issue\n\n```typescript\nit(\"should [correct behavior] when [condition]\", async () => {\n  \u002F\u002F Reproduce the bug scenario\n  \u002F\u002F Verify it's now fixed\n});\n```\n````\n\n### Test 2: Regression test\n\n```typescript\nit(\"should not regress [related functionality]\", async () => {\n  \u002F\u002F Ensure fix doesn't break other things\n});\n```\n\n````\n\n---\n\n### Refactor Template\n\nUse the Feature template with these modifications:\n\n**Title format**: `refactor: [brief description]`\n\n**Add after \"Summary\"**:\n\n```markdown\n## Background\n\n[Why is this refactor needed? What triggered it?]\n\n### Review Feedback Being Addressed\n\n> [Quote the review comment that prompted this work]\n\n- Original PR: #XXX\n- Comment by: @reviewer\n````\n\n**Add to \"Acceptance Criteria\"**:\n\n```markdown\n- [ ] No breaking changes to public APIs\n- [ ] All existing tests still pass without modification\n- [ ] Performance not degraded (if applicable)\n```\n\n---\n\n## After Generation\n\nAfter generating the issue content:\n\n1. **Show preview** to user\n2. **Ask for modifications** if needed\n3. **Create issue** with appropriate labels:\n\n   ```bash\n   # Feature\n   gh issue create --title \"feat: [title]\" --body \"[content]\" \\\n     --label \"enhancement\" --label \"complexity:[level]\"\n\n   # Bug\n   gh issue create --title \"fix: [title]\" --body \"[content]\" \\\n     --label \"bug\" --label \"priority:[level]\"\n\n   # Refactor\n   gh issue create --title \"refactor: [title]\" --body \"[content]\" \\\n     --label \"refactor\" --label \"complexity:[level]\"\n   ```\n\n4. **Report issue number** to user\n\n---\n\n## Key Principles\n\n1. **Self-contained**: Issues should have everything an agent needs to work autonomously\n2. **TDD-first**: Always include test specifications before implementation\n3. **Complete lifecycle**: Agent Instructions cover implementation through merge\n4. **No shortcuts**: ALL review comments must be addressed, including trivial\u002Fnitpicks\n5. **Out-of-scope = gold**: Comments marked out-of-scope often contain the best insights\n6. **Iterate until done**: PR is not complete until ALL threads are resolved\n","# Create GitHub Issue Skill\n\nCreate comprehensive, well-structured GitHub issues with embedded agent instructions for autonomous PR lifecycle management.\n\n## Overview\n\nThis skill generates GitHub issues that are self-contained work packets. Each issue includes:\n\n1. **Problem\u002FFeature specification** with clear scope\n2. **Technical specification** with types, schemas, and API design\n3. **TDD Implementation Plan** with test-first cycles\n4. **Acceptance Criteria** checklist\n5. **Agent Instructions** for complete PR lifecycle (implementation → review → merge)\n\n## Usage\n\n```\n\u002Fcreate-issue\n```\n\n## Interactive Flow\n\n### Step 1: Issue Type\n\nAsk the user:\n\n```\nWhat type of issue is this?\n1. Feature - New functionality\n2. Bug - Something broken\n3. Refactor - Improving existing code\n```\n\n### Step 2: Brief Description\n\n```\nBrief description of the problem or feature? (1-2 sentences)\n```\n\n### Step 3: Complexity Assessment\n\n```\nWhat's the estimated complexity?\n1. Simple (\u003C 1 day)\n2. Medium (2-5 days)\n3. Complex (> 1 week)\n```\n\n### Step 4: Context Gathering\n\n```\nAny related files, services, or issues I should reference?\n(Or say \"explore codebase\" and I'll investigate)\n```\n\n### Step 5: Generate Issue\n\nBased on inputs, generate the full issue using the appropriate template below.\n\n---\n\n## Issue Templates\n\n### Feature Template\n\n````markdown\n## Summary\n\n[1-2 sentence description]\n\n**Complexity**: [simple|medium|complex]\n**Estimated Effort**: [X days]\n\n---\n\n## Problem\n\n[What problem does this solve? Why is it needed?]\n\n### Evidence\n\n[Logs, metrics, user reports, or reasoning]\n\n### Scope\n\n- IN SCOPE: [what's included]\n- OUT OF SCOPE: [what's explicitly NOT included]\n\n---\n\n## Architecture Decision\n\n**Decision**: [What approach will be taken]\n**Rationale**: [Why this approach, why NOT alternatives]\n\n---\n\n## Technical Specification\n\n### Types\u002FInterfaces\n\n```typescript\n\u002F\u002F Key type definitions\n```\n````\n\n### Zod Schemas (if applicable)\n\n```typescript\n\u002F\u002F Validation schemas\n```\n\n### API Endpoints (if applicable)\n\n| Method | Path | Description |\n| ------ | ---- | ----------- |\n\n### Database Changes (if applicable)\n\n[Schema changes, migrations needed]\n\n---\n\n## TDD Implementation Plan\n\n### Cycle 1: [Happy Path]\n\n```typescript\nit(\"should [expected behavior]\", async () => {\n  \u002F\u002F Test code\n});\n```\n\n### Cycle 2: [Error Handling]\n\n```typescript\nit(\"should handle [error case]\", async () => {\n  \u002F\u002F Test code\n});\n```\n\n### Cycle 3: [Edge Cases]\n\n### Cycle 4: [Integration]\n\n---\n\n## Error Handling\n\n| Scenario | Behavior | Logging |\n| -------- | -------- | ------- |\n\n---\n\n## Implementation Phases\n\n### Phase 1: [Core] (High Priority)\n\n- [ ] Task 1\n- [ ] Task 2\n\n### Phase 2: [Enhancement] (Medium Priority)\n\n- [ ] Task 3\n\n---\n\n## Files to Create\u002FModify\n\n- **NEW**: `path\u002Fto\u002Fnew\u002Ffile.ts`\n- `path\u002Fto\u002Fexisting\u002Ffile.ts` - [what changes]\n\n---\n\n## Acceptance Criteria\n\n- [ ] All TDD cycles implemented with passing tests\n- [ ] Zero TypeScript errors (`pnpm typecheck`)\n- [ ] Zero lint warnings (`pnpm lint`)\n- [ ] All tests pass (`pnpm test --run`)\n- [ ] **JSDoc documentation** added to all new\u002Fmodified services\n- [ ] **`docs\u002FSERVICE_INVENTORY.md`** updated (if new\u002Fmodified service)\n- [ ] **Mock factories** added\u002Fupdated (if new service)\n- [ ] PR created and all CI checks pass\n- [ ] **ALL code review comments addressed** (see Agent Instructions)\n- [ ] All review threads resolved\n- [ ] PR approved and merged\n\n---\n\n## Agent Instructions\n\n**CRITICAL**: Follow this protocol when implementing this issue. A PR is NOT complete until ALL steps are done.\n\n### Phase 0: Research (BEFORE writing any code)\n\n**Read these files first to avoid reinventing the wheel:**\n\n1. **Service Inventory** - Check for existing services that might already do what you need:\n\n   ```bash\n   # Read the service inventory\n   cat docs\u002FSERVICE_INVENTORY.md\n   # Or search for specific functionality\n   grep -i \"embedding\\|search\\|cache\" docs\u002FSERVICE_INVENTORY.md\n   ```\n\n2. **Mock Factories** - Review existing mocks to reuse patterns:\n\n   ```bash\n   ls src\u002Ftest-utils\u002Ffactories\u002F\n   ```\n\n3. **Similar Services** - Find services with similar patterns:\n   ```bash\n   # Find orchestrator patterns\n   ls src\u002Flib\u002Fservices\u002F*-orchestrator*.ts\n   # Find persistence patterns\n   ls src\u002Flib\u002Fservices\u002F*-persistence*.ts\n   ```\n\n**Why this matters**: Reusing existing services and patterns saves time, maintains consistency, and prevents duplicate code.\n\n### Phase A: Implementation\n\n1. Create feature branch from main: `git checkout -b feat\u002F[short-name]`\n2. Follow TDD cycles exactly as specified above\n3. **Add JSDoc documentation** to all new\u002Fmodified services\n4. Run local validation: `pnpm lint && pnpm typecheck && pnpm test --run`\n5. **Update service inventory** (if new service)\n6. Create PR with comprehensive description using `\u002Fcreate-pr`\n\n### Phase B: Code Review Iteration\n\n**Wait for code reviews before proceeding. Do NOT mark complete after pushing code.**\n\nFor EACH code review iteration:\n\n1. **Fetch ALL comments** (including trivial, nitpicks, and out-of-scope):\n\n   ```bash\n   PR_NUMBER=XXX\n   OWNER=$(gh repo view --json owner -q .owner.login)\n   REPO=$(gh repo view --json name -q .name)\n   gh api \"repos\u002F$OWNER\u002F$REPO\u002Fpulls\u002F$PR_NUMBER\u002Fcomments\" --paginate\n   ```\n\n2. **Address ALL comments by category**:\n\n   | Type                   | Action                                               |\n   | ---------------------- | ---------------------------------------------------- |\n   | Critical\u002FMajor         | Fix immediately                                      |\n   | Medium\u002FMinor           | Fix before merge                                     |\n   | **Trivial\u002FNitpick**    | **Fix these too!** Do NOT skip                       |\n   | **Out-of-scope**       | **Investigate thoroughly** - often the BEST insights |\n\n3. **For each comment**:\n   - **\u003C 1 day of work** → Implement the fix in this PR\n   - **> 1 day OR architectural** → Create a new GitHub issue, link in response\n   - **Disagree** → Reply explaining why with technical reasoning\n\n4. **After making changes**:\n\n   ```bash\n   pnpm lint && pnpm typecheck && pnpm test --run\n   git add . && git commit -m \"fix: address review feedback\" && git push\n   ```\n\n5. **Respond to EVERY comment thread individually**:\n\n   ```bash\n   COMMENT_ID=XXX\n   CURRENT_USER=$(gh api user -q '.login')\n   gh api \"\u002Frepos\u002F$OWNER\u002F$REPO\u002Fpulls\u002F$PR_NUMBER\u002Fcomments\u002F$COMMENT_ID\u002Freplies\" \\\n     -X POST \\\n     -f body=\"Fixed in commit $(git rev-parse --short HEAD). [explanation]\n\n   *(Response by Claude on behalf of @$CURRENT_USER)*\"\n   ```\n\n6. **Wait for next review cycle** - Do NOT resolve threads yourself\n\n7. **Repeat steps 1-6** until reviewer confirms satisfaction\n\n### Phase C: Thread Resolution\n\nOnly AFTER reviewer approval:\n\n1. Re-fetch all threads to get current IDs\n2. Resolve each thread:\n\n   ```bash\n   THREAD_ID=\"PRRT_xxx\"\n   gh api graphql -f threadId=\"$THREAD_ID\" -f query='\n     mutation($threadId: ID!) {\n       resolveReviewThread(input: {threadId: $threadId}) {\n         thread { id isResolved }\n       }\n     }'\n   ```\n\n3. Verify all threads resolved before proceeding\n\n### Phase D: Merge Readiness\n\nPR is ready for merge ONLY when ALL are true:\n\n- [ ] All CI checks pass (green)\n- [ ] **EVERY** code review comment addressed (including trivial\u002Fout-of-scope)\n- [ ] **EVERY** thread has individual response\n- [ ] All threads are resolved (after reviewer approval)\n- [ ] GitHub issues created for any deferred work (> 1 day)\n- [ ] No pending reviewer comments awaiting response\n\n### Phase E: Squash Merge and Cleanup\n\n**IMPORTANT**: Always use squash merge, never regular merge.\n\n1. **Squash and merge** the PR (combines all commits into one clean commit):\n\n   ```bash\n   # Via GitHub CLI\n   gh pr merge $PR_NUMBER --squash --delete-branch\n\n   # Or via GitHub web UI:\n   # Click \"Squash and merge\" (NOT \"Merge\" or \"Rebase and merge\")\n   ```\n\n2. **Delete the feature branch** (automatically done with --delete-branch flag):\n\n   ```bash\n   # If branch wasn't auto-deleted:\n   git push origin --delete feat\u002F[branch-name]\n   git branch -d feat\u002F[branch-name]\n   ```\n\n3. **Update local main**:\n\n   ```bash\n   git checkout main\n   git pull origin main\n   ```\n\n### Reference\n\nSee the `\u002Fmetaswarm:handle-pr-comments` command for detailed protocol.\n\n---\n\n## Related Issues\n\n- [Link to related issues]\n\n## References\n\n- [Link to relevant docs, specs, or PRs]\n\n````\n\n---\n\n### Bug Template\n\nUse the Feature template with these modifications:\n\n**Title format**: `fix: [brief description]`\n\n**Replace \"Problem\" section with**:\n\n```markdown\n## Bug Report\n\n**Priority**: [P0-Critical|P1-High|P2-Medium|P3-Low]\n**Affected Users**: [scope of impact]\n**First Reported**: [date\u002Fsource]\n\n### Expected Behavior\n\n[What should happen]\n\n### Actual Behavior\n\n[What actually happens]\n\n### Steps to Reproduce\n\n1. Step 1\n2. Step 2\n3. Step 3\n\n### Root Cause Analysis\n\n[If known, explain why this is happening]\n\n### Evidence\n\n[Logs, stack traces, screenshots]\n````\n\n**Replace \"TDD Implementation Plan\" with**:\n\n````markdown\n## Test Cases\n\n### Test 1: Verify fix for reported issue\n\n```typescript\nit(\"should [correct behavior] when [condition]\", async () => {\n  \u002F\u002F Reproduce the bug scenario\n  \u002F\u002F Verify it's now fixed\n});\n```\n````\n\n### Test 2: Regression test\n\n```typescript\nit(\"should not regress [related functionality]\", async () => {\n  \u002F\u002F Ensure fix doesn't break other things\n});\n```\n\n````\n\n---\n\n### Refactor Template\n\nUse the Feature template with these modifications:\n\n**Title format**: `refactor: [brief description]`\n\n**Add after \"Summary\"**:\n\n```markdown\n## Background\n\n[Why is this refactor needed? What triggered it?]\n\n### Review Feedback Being Addressed\n\n> [Quote the review comment that prompted this work]\n\n- Original PR: #XXX\n- Comment by: @reviewer\n````\n\n**Add to \"Acceptance Criteria\"**:\n\n```markdown\n- [ ] No breaking changes to public APIs\n- [ ] All existing tests still pass without modification\n- [ ] Performance not degraded (if applicable)\n```\n\n---\n\n## After Generation\n\nAfter generating the issue content:\n\n1. **Show preview** to user\n2. **Ask for modifications** if needed\n3. **Create issue** with appropriate labels:\n\n   ```bash\n   # Feature\n   gh issue create --title \"feat: [title]\" --body \"[content]\" \\\n     --label \"enhancement\" --label \"complexity:[level]\"\n\n   # Bug\n   gh issue create --title \"fix: [title]\" --body \"[content]\" \\\n     --label \"bug\" --label \"priority:[level]\"\n\n   # Refactor\n   gh issue create --title \"refactor: [title]\" --body \"[content]\" \\\n     --label \"refactor\" --label \"complexity:[level]\"\n   ```\n\n4. **Report issue number** to user\n\n---\n\n## Key Principles\n\n1. **Self-contained**: Issues should have everything an agent needs to work autonomously\n2. **TDD-first**: Always include test specifications before implementation\n3. **Complete lifecycle**: Agent Instructions cover implementation through merge\n4. **No shortcuts**: ALL review comments must be addressed, including trivial\u002Fnitpicks\n5. **Out-of-scope = gold**: Comments marked out-of-scope often contain the best insights\n6. **Iterate until done**: PR is not complete until ALL threads are resolved\n",{"name":5,"description":7},"main","a298c929b6cbd662e1fce54302ce520d5ceea1a5","tools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fcreate-issue","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain","https:\u002F\u002Fgithub.com\u002FPrekzursil","2026-11-02 14:30:57",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add Prekzursil\u002Fagent-skills-toolchain --skill create-issue",{"tool":60,"command":61},"bunx","bunx skills add Prekzursil\u002Fagent-skills-toolchain --skill create-issue",{"tool":63,"command":64},"pnpm","pnpm dlx skills add Prekzursil\u002Fagent-skills-toolchain --skill create-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fcreate-issue\u002FSKILL.md",true,[],[69,91,118,145,158,173],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":43},"01M6DF7D7478R55P46REYH4QAC","clarify-requirements","Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fworkspace-hooks\u002Fskills\u002Fclarify-requirements\u002FSKILL.md",[],[76,77,78,79,80,81,82,83,84,85,86,87,88,89,90],"clarify requirements","clarify","requirements","risk","options","task","prompts","goal","scanning","use","context","repo","injection","execution","file",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":98,"publishedAt":43},"01M6DF79CA4BHJS66J8EZDBPWJ","openmm-md","Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein \u002F protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fmcp\u002Fopenmm-md-mcp\u002Fskill\u002Fopenmm-md\u002FSKILL.md",[97],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[99,100,101,102,103,104,105,106,107,108,109,110,111,112,85,113,114,115,116,117],"openmm md","how","decision","pick","linux","analyze","tool","stack","open","NVIDIA","gpu","license","workflow","windows","free","molecular dynamics","local","do","MCP",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":130,"publishedAt":43},"01M6DF76C1MG85VEWP8VZCBNMN","visual-review","Take screenshots of web pages and UI using Playwright for visual review and iteration","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fvisual-review\u002FSKILL.md",[124,127],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[131,132,133,134,135,136,137,138,139,140,100,141,142,143,144],"review","visual","visual review","pages","web","false","iteration","take","check","slides","ui","screenshot","playwright","screenshots",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":43},"01M6DF73AQVCBZKEN0YXEX9FXP","status","Diagnostic status report — shows metaswarm installation state, project setup, and potential issues","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstatus\u002FSKILL.md",[],[147,152,153,154,155,156,35,157],"setup","report","project","installation","project setup","state",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":165,"publishedAt":43},"01M6DF6X6C2XB0P6GX76P7TTYV","start","Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstart\u002FSKILL.md",[164],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[160,166,81,28,167,168,85,169,170,171,172],"start issue","ready","work on issue","user","work","work on","development",{"skillNo":174,"name":152,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":43},"01M6DF6QMJ9AJKFKHHKRT005PQ","Interactive project setup — detects your project, configures metaswarm, writes project-local files","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fsetup\u002FSKILL.md",[],[152,154,115,179,156,180],"files","interactive"]