mikeparcewski/wicked-garden / skills/engineering
wicked-garden-engineering
VerifiedEngineering domain skill: code review, architecture analysis, debugging, implementation planning, documentation, release PRs and scaffolds. Use when: "review this code / file / diff" (quality, patterns, maintainability; --focus, --persona, --scenarios); "review the architecture of X" / "evaluate component boundaries, coupling, or layer violations" (--scope module|service|system); "debug this error / bug / unexpected behavior" (root cause, reproduction, fix, prevention); "plan this change" / "implementation plan with file changes, risks and tests before writing code"; "generate API docs / README / guide / inline comments" (--type api|readme|guide|inline) or "docs drifted from code"; "prepare a release PR" (never tags or publishes); "scaffold a new CLI / service / library". NOT for reviewing an AI agent system (agentic review), a UI (product ux-review), a go/no-go verdict (archetype review), greenfield design (the solution-architect worker) or scaffolding a new MCP server (wicked-garden-mcp-scaffold).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.7 KB |
| refs/arch.md | markdown | 4.5 KB |
| refs/conformance.md | markdown | 3.8 KB |
| refs/debug.md | markdown | 4.0 KB |
| refs/docs.md | markdown | 5.8 KB |
| refs/engineering-checklists.md | markdown | 2.7 KB |
| refs/engineering-templates.md | markdown | 1.2 KB |
| refs/plan.md | markdown | 4.1 KB |
| refs/release.md | markdown | 7.4 KB |
| refs/review.md | markdown | 7.4 KB |
| refs/scaffold.md | markdown | 5.6 KB |
refs/engineering-checklists.md
View on GitHub---
phase_relevance: ["design", "build"]
archetype_relevance: ["*"]
---
# Engineering Review Checklists
## Structure Checklist
- [ ] Follows established patterns
- [ ] Appropriate abstraction level
- [ ] Clear boundaries/interfaces
- [ ] No circular dependencies
- [ ] Separation of concerns
## Quality Checklist
- [ ] Clear naming
- [ ] No unnecessary duplication
- [ ] Appropriate comments (not excessive)
- [ ] Consistent style
- [ ] Single responsibility
## Error Handling Checklist
- [ ] Errors handled appropriately
- [ ] No swallowed exceptions
- [ ] Meaningful error messages
- [ ] Recovery strategies
## Maintainability Checklist
- [ ] Easy to understand
- [ ] Easy to modify
- [ ] No magic numbers/strings
- [ ] Configuration externalized
## Performance Checklist
- [ ] No obvious N+1 queries
- [ ] Appropriate data structures
- [ ] No unnecessary computation
- [ ] Caching where appropriate
## Common Issues to Watch For
### Code Smells
- Magic numbers/strings (use constants)
- Long functions (break into smaller)
- Deep nesting (refactor to early returns)
- Duplicated code (extract to shared)
- Poor naming (rename for clarity)
- Missing error handling
- Resource leaks (unclosed connections)
### Good Patterns
- Single responsibility
- Clear separation of concerns
- Defensive programming
- Meaningful abstractions
- Consistent error handling
## Agent Overstepping Checklist
Detect patterns where AI agents make changes beyond what was requested:
### Unnecessary Changes (HIGH)
- [ ] Code modified that wasn't part of the task scope
- [ ] Working logic replaced with "simplified" alternatives
- [ ] Variable/function renames unrelated to the task
- [ ] Import reorganization or style changes outside scope
- [ ] Added abstractions or helpers for one-time operations
### Commented-Out Code (HIGH)
- [ ] Working code commented out instead of removed
- [ ] Logic replaced with TODO comments
- [ ] Conditional blocks disabled via comments
- [ ] Backward-compatibility shims with "// removed" markers
### Over-Engineering (MEDIUM)
- [ ] New configuration options nobody asked for
- [ ] Feature flags for non-flagged features
- [ ] Added error handling for impossible scenarios
- [ ] Premature abstractions ("just in case" utilities)
- [ ] Extra validation layers beyond system boundaries
### Scope Creep Indicators
- [ ] Files modified that weren't mentioned in the task
- [ ] Refactoring mixed into bug fixes
- [ ] Style changes bundled with feature work
- [ ] Documentation updates for unchanged code
## Severity Guidelines
- **HIGH**: Will cause bugs, broken patterns, production issues, major maintainability problems
- **MEDIUM**: Should fix, not blocking, tech debt accumulation
- **LOW**: Nice to have, style preferences, minor improvements
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |