wsbaser

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.

Guided workflow for creating a new subagent .md file in plugins/wsbaser/agents/

Coordinate a team of coding and review agents to implement features from spec files

Full development workflow from Jira story to implementation with multi-agent review

Audit and improve CLAUDE.md files — score quality, propose fixes, apply with approval

Reviews code for Clean Architecture violations, SOLID principles at module/service level, DDD boundary integrity, and separation of concerns

Reviews code for DRY violations, SOLID principles at method/class level, code smells, and clean code practices

Simplifies code for clarity and maintainability without changing behavior. Focuses on a single component's files (.razor, .razor.cs, .razor.scss, .razor.js/.ts).

Challenges assumptions and stress-tests decisions during spec implementation. Invoke proactively at key decision points to surface risks, failure modes, and spec misinterpretations before they become problems.

Block-by-block analysis of uncommitted changes against spec requirements. Verifies every decision is correct, justified, and optimal; finds reuse opportunities and spec gaps.

Produces optimized Gherkin scenarios covering critical paths, edge cases, and error handling. Use in planning phase before writing test code. Trigger: "write scenarios", "plan tests", "what to test", "give me gherkin", or analyze a branch for test coverage. Do NOT trigger for implementing test code, fixing tests, or Gherkin syntax questions.

Produces a verdict HTML bug report (MITIGATED/CONFIRMED/INCONCLUSIVE) with call chain, network summary, and code snippet. Writes to .reports/{slug}.html. Use for single bugs; use generate-test-report for multi-scenario suites.

Produces an Allure-style multi-scenario HTML report at .reports/{slug}.html with sidebar, step drill-down, issue cards, and a copy-fix-prompt button. Invoke after browser testing or on "generate test report". Use generate-bug-report for single-bug reports.

Interview user to capture feature requirements, write spec to specs/. Add --plan for phased implementation plan. Trigger: spec a feature, share a ticket/doc/design link, or say "plan this out".

Appends short contextual lessons to responses. Supports any language or custom topic. Trigger: user asks for recurring lessons, mentions /microlearn, or wants to learn a topic during coding.