feat: restore review and planning bundles

This commit is contained in:
Affaan Mustafa
2026-04-05 17:51:56 -07:00
parent 56bd57c543
commit 8a3651588a
15 changed files with 472 additions and 17 deletions

49
commands/feature-dev.md Normal file
View File

@@ -0,0 +1,49 @@
---
description: Guided feature development with codebase understanding and architecture focus
---
A structured feature-development workflow that emphasizes understanding existing code before writing new code.
## Phases
### 1. Discovery
- read the feature request carefully
- identify requirements, constraints, and acceptance criteria
- ask clarifying questions if the request is ambiguous
### 2. Codebase Exploration
- use `code-explorer` to analyze the relevant existing code
- trace execution paths and architecture layers
- understand integration points and conventions
### 3. Clarifying Questions
- present findings from exploration
- ask targeted design and edge-case questions
- wait for user response before proceeding
### 4. Architecture Design
- use `code-architect` to design the feature
- provide the implementation blueprint
- wait for approval before implementing
### 5. Implementation
- implement the feature following the approved design
- prefer TDD where appropriate
- keep commits small and focused
### 6. Quality Review
- use `code-reviewer` to review the implementation
- address critical and important issues
- verify test coverage
### 7. Summary
- summarize what was built
- list follow-up items or limitations
- provide testing instructions

37
commands/review-pr.md Normal file
View File

@@ -0,0 +1,37 @@
---
description: Comprehensive PR review using specialized agents
---
Run a comprehensive multi-perspective review of a pull request.
## Usage
`/review-pr [PR-number-or-URL] [--focus=comments|tests|errors|types|code|simplify]`
If no PR is specified, review the current branch's PR. If no focus is specified, run the full review stack.
## Steps
1. Identify the PR:
- use `gh pr view` to get PR details, changed files, and diff
2. Find project guidance:
- look for `CLAUDE.md`, lint config, TypeScript config, repo conventions
3. Run specialized review agents:
- `code-reviewer`
- `comment-analyzer`
- `pr-test-analyzer`
- `silent-failure-hunter`
- `type-design-analyzer`
- `code-simplifier`
4. Aggregate results:
- dedupe overlapping findings
- rank by severity
5. Report findings grouped by severity
## Confidence Rule
Only report issues with confidence >= 80:
- Critical: bugs, security, data loss
- Important: missing tests, quality problems, style violations
- Advisory: suggestions only when explicitly requested