Claude-skill-registry local-review
Review current changes against project guidelines before PR
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/local-review" ~/.claude/skills/majiayu000-claude-skill-registry-local-review && rm -rf "$T"
manifest:
skills/data/local-review/SKILL.mdsource content
Local Review
Perform a comprehensive self-review of changes before creating a pull request.
Instructions
-
Gather Context
- Get current branch name
- Find associated workflow folder
- Read the original issue/concept and plan
-
Get Changes
- Run
to see all changesgit diff main...HEAD - Run
to see commitsgit log main...HEAD --oneline - List all modified files
- Run
-
Review Against Guidelines
Review the code against REVIEW_GUIDELINES.md, which covers:
- Architecture checklist
- Code style checklist
- Configuration precedence checklist
- Anti-over-engineering checklist
- Testing checklist
- Commit message checklist
- Documentation checklist
-
Code Quality Checks
# Build check go build ./... # Test check go test ./... # Format check go fmt ./... # Vet check go vet ./... -
Generate Review Report
Create a summary with:
# Local Review: <branch-name> ## Summary - Files changed: <count> - Lines added: <count> - Lines removed: <count> - Commits: <count> ## Checklist Results ### Passed - <item 1> - <item 2> ### Issues Found - [ ] <issue 1> - <file:line> - <description> - [ ] <issue 2> - <file:line> - <description> ### Warnings - <warning 1> ## Quality Checks - Build: PASS/FAIL - Tests: PASS/FAIL (<count> passed) - Format: PASS/FAIL - Vet: PASS/FAIL ## Recommendations 1. <recommendation> 2. <recommendation> ## Ready for PR? <YES/NO - explain if NO> -
Report Findings
- If issues found, list them with specific file:line references
- Suggest fixes for each issue
- Indicate if changes are PR-ready
Issue Categories
Blocking (must fix)
- Test failures
- Build errors
- Missing error handling
- Security concerns
- Guideline violations
Warnings (should fix)
- Missing documentation
- Inconsistent naming
- Suboptimal patterns
Suggestions (nice to have)
- Code clarity improvements
- Additional test cases
- Performance optimizations