Philosophy-aware PR reviews checking alignment with amplihack principles. Use when reviewing PRs to ensure ruthless simplicity, modular design, and zero-BS implementation. Suggests simplifications, identifies over-engineering, verifies brick module structure. Posts detailed, constructive review comments with specific file:line references.
Philosophy-aware pull request reviews that check alignment with amplihack principles. Use when reviewing PRs to ensure ruthless simplicity, modular design, and zero-BS implementation. Suggests simplifications, identifies over-engineering, verifies brick module structure.
Claude, review this PR for philosophy alignment:
- Check for over-engineering
- Verify module structure
- Suggest simplifications
Claude will:
This skill reviews for:
Ruthless Simplicity
Modular Architecture (Brick & Studs)
Zero-BS Implementation
Test Coverage
Documentation
Claude, review this code for philosophy alignment.
Or:
Claude, check this PR (#123) against our development philosophy.
Claude provides:
Review the suggestions and:
Claude, I've addressed the issues. Can you re-review?
Once philosophy aligned, ready to merge!
DETECTED: Unnecessary abstraction
ISSUE: Base class for 2 implementations
SUGGESTION: Use simple direct classes
DETECTED: New public function untested
ISSUE: validate_token() has no tests
SUGGESTION: Add tests for true/false/edge cases
DETECTED: TODO comment at line 34
ISSUE: Incomplete work shouldn't be merged
SOLUTION: Implement it or remove the comment
DETECTED: New module without specification
ISSUE: Module can't be regenerated
ACTION: Create Specs/module-name.md
RUTHLESS SIMPLICITY: ✓ PASS
- Code is straightforward
- Each function has single purpose
- No over-abstraction
MODULAR ARCHITECTURE: ✓ PASS
- Clear single responsibility
- Public interface minimal
- Dependencies explicit
ZERO-BS IMPLEMENTATION: ⚠ NEEDS WORK
- 2 TODO comments (lines 45, 67)
- 1 swallowed exception (line 52)
TEST COVERAGE: ✗ GAPS
- Missing edge case tests
- Coverage at 72%
DOCUMENTATION: ⚠ PARTIAL
- Module spec missing
- Good docstrings overall
VERDICT: NEEDS IMPROVEMENTS BEFORE MERGE
All reviews anchor in:
See ~/.amplihack/.claude/context/PHILOSOPHY.md for complete philosophy.
The skill:
Through this skill, you learn:
Q: Does this check Python style? A: No. Use linters for style (black, flake8). This checks philosophy.
Q: Can I disagree with feedback? A: Absolutely! That's how we improve. Explain your reasoning and let's discuss.
Q: What if I think the code is fine? A: You might be right. Ask Claude to explain the principle and see if you learn something.
Q: How often should I use this? A: For significant changes. Small bug fixes might not need a full review.
Q: Can I request re-review? A: Yes, after making changes: "Re-review my changes to see if issues are addressed"
Q: What if I don't understand feedback? A: Ask Claude to explain more clearly or provide additional examples.
This skill evolves based on usage:
Share learnings in ~/.amplihack/.claude/context/DISCOVERIES.md.
That's it! Philosophy-aware code review in action.
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer