From wicked-garden
Systematic review methodology for agentic codebases with issue detection, analysis, and reporting. Use when: "review agentic code", "audit agent system", "check agent quality", "agentic code review"
npx claudepluginhub mikeparcewski/wicked-garden --plugin wicked-gardenThis skill uses the workspace's default tool permissions.
Systematic approach to reviewing agentic systems and codebases for issues, risks, and improvement opportunities.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Systematic approach to reviewing agentic systems and codebases for issues, risks, and improvement opportunities.
Goal: Identify all potential issues
Activities:
Tools:
Deliverable: Raw issue inventory
Goal: Understand each issue's impact and root cause
For Each Issue:
refs/issue-taxonomy-reliability-safety.md and refs/issue-taxonomy-quality-testing.md)Analysis Framework:
Deliverable: Analyzed issue list with severity and impact
Goal: Prioritize issues for remediation
Severity Levels:
Critical (P0): Security vulnerabilities, data loss risks, system crashes, compliance violations. Fix immediately.
High (P1): Reliability issues, performance problems, cost inefficiencies, safety gaps. Fix within 1 week.
Medium (P2): Code quality issues, minor performance issues, missing observability. Fix within 1 month.
Low (P3): Style issues, optimization opportunities, nice-to-have features. Backlog.
Prioritization Matrix:
Impact vs Effort:
Low Effort High Effort
High Quick Wins Major Projects
Impact (Do First) (Plan)
Low Easy Wins Avoid
Impact (Do Later) (Skip)
Deliverable: Prioritized roadmap
Goal: Communicate findings effectively to stakeholders
Report Components:
Deliverable: Comprehensive review report
See refs/deliverable-templates.md for complete templates.
Critical:
High:
Medium:
Low:
See refs/issue-taxonomy-reliability-safety.md and refs/issue-taxonomy-quality-testing.md for complete classification guide.
For each issue, document:
## Issue: [Short Title]
**ID:** ISSUE-001
**Severity:** Critical | High | Medium | Low
**Category:** Reliability | Security | Safety | Cost | Performance | Quality
**Component:** [Which agent/module]
### Description
[What is the issue?]
### Evidence
[Code snippets, logs, metrics]
### Impact
[What are the consequences?]
### Root Cause
[Why does this exist?]
### Recommendation
[How to fix it?]
### Effort Estimate
[Hours/Days/Weeks]
### Priority
[P0/P1/P2/P3]
refs/issue-taxonomy-reliability-safety.md and refs/issue-taxonomy-quality-testing.md - Complete issue category reference and anti-pattern detectionrefs/deliverable-templates.md - Detailed report templates and review checklist