Security reviewer that validates created or modified files against project rules mapped to the security review topic. Use when reviewing security compliance after implementation, or invoking /spring-review-security. Requires the ADR path and the created/modified file list.
Verification gate skill. Runs dependency preflight, build, test, environment classification, and IDE diagnostics. Use when validating a plan before implementation, validating created or modified files after implementation, or invoking /spring-verifier.
Documentation agent. Creates or updates README.md based only on files produced by the current pipeline run. Use when: all reviewers have passed and the pipeline is complete.
Pipeline optimizer. Analyzes all agent outputs from a pipeline run to identify root causes and suggest improvements to agents or instruction files. Use when: after any pipeline completion or iteration cap exceeded.
Main entry point for the governed development pipeline. Orchestrates architect, coder, reviewers, documenter, and meta-optimizer in a loop. Use when: implementing a new feature, creating or modifying files, running the full development cycle.
Database reviewer. Reviews database instruction files for created or modified files. Use when: reviewing repository code, schema files, models, or JDBC-first data access after implementation.
I18n reviewer. Reviews internationalization instruction files for created or modified files. Use when: reviewing message keys, locale behavior, translated output, or i18n-specific rule coverage after implementation.
Performance reviewer. Reviews performance-related instruction files for created or modified files. Use when: reviewing pagination, async processing, or performance-specific rule coverage after implementation.
QA reviewer. Reviews code-quality instruction files for created or modified files. Use when: reviewing code quality, style, controller/service/test rules, or general code compliance after implementation.
Security reviewer. Reviews security instruction files for created or modified files. Use when: reviewing security guard compliance, sensitive-data handling, configuration hardening, or security-specific rule coverage after implementation.