Code Coaching
Review "$ARGUMENTS" through the lens of a senior software engineer. Provide mentorship feedback on code quality, architecture patterns, security, performance, and testing.
Prerequisites
None — this is a utility skill that can run anytime.
Process
Read the target:
- Read the source code files specified in "$ARGUMENTS"
- If it's a directory, read the key files
- Understand the context: what does this code do?
Read reference material:
- Read
plugins/coaching/shared/code-principles.md for engineering principles
- Read
plugins/coaching/shared/feedback-format.md for output structure
Evaluate against engineering principles:
- SOLID: Single responsibility, open/closed, Liskov, interface segregation, dependency inversion
- Clean code: Naming clarity, function size, abstraction levels, self-documenting code
- DRY/YAGNI/KISS: Appropriate abstraction level, no premature optimization
- Security: Input validation, injection prevention, secrets management, auth patterns
- Performance: N+1 queries, appropriate data structures, caching, lazy loading
- Database: Normalization, indexing, query patterns, transactions
- Testing: Coverage, behavior vs. implementation testing, test quality
- Error handling: Appropriate error types, no swallowed errors, graceful degradation
Write the coaching report to .metapowers/coaching/$ARGUMENTS/code-review.md following the feedback format.
Output
The code coaching report written to .metapowers/coaching/$ARGUMENTS/code-review.md. Present the score and top 3 suggestions to the user.
1---2name: code3description: Review code through the lens of a senior engineer4---56# Code Coaching78Review "$ARGUMENTS" through the lens of a senior software engineer. Provide mentorship feedback on code quality, architecture patterns, security, performance, and testing.910## Prerequisites1112None — this is a utility skill that can run anytime.1314## Process15161. **Read the target:**17 - Read the source code files specified in "$ARGUMENTS"18 - If it's a directory, read the key files19 - Understand the context: what does this code do?20212. **Read reference material:**22 - Read `plugins/coaching/shared/code-principles.md` for engineering principles23 - Read `plugins/coaching/shared/feedback-format.md` for output structure24253. **Evaluate against engineering principles:**26 - **SOLID:** Single responsibility, open/closed, Liskov, interface segregation, dependency inversion27 - **Clean code:** Naming clarity, function size, abstraction levels, self-documenting code28 - **DRY/YAGNI/KISS:** Appropriate abstraction level, no premature optimization29 - **Security:** Input validation, injection prevention, secrets management, auth patterns30 - **Performance:** N+1 queries, appropriate data structures, caching, lazy loading31 - **Database:** Normalization, indexing, query patterns, transactions32 - **Testing:** Coverage, behavior vs. implementation testing, test quality33 - **Error handling:** Appropriate error types, no swallowed errors, graceful degradation34354. **Write the coaching report** to `.metapowers/coaching/$ARGUMENTS/code-review.md` following the feedback format.3637## Output3839The code coaching report written to `.metapowers/coaching/$ARGUMENTS/code-review.md`. Present the score and top 3 suggestions to the user.
bromso