Add, update, or deduplicate content in a markdown or plain-text file while preserving its structure and formatting. Use when the user asks to insert or merge content into a specific file, or invokes /add-content-to-file. Requires a user-provided target file and the content to add.
Remove only artifacts created in the current chat so the workspace can restart cleanly. Use when the user asks for a clean slate, cleanup of chat-created files, or invokes /clean-slate-workspace. Optional: scope notes or exclusions.
Cluster uncommitted changes into feature-scoped Conventional Commits, present a commit plan, and execute it only after explicit approval. Use when the user asks to prepare, organize, or plan commits, or invokes /prepare-commit-messages. Optional input: a path or feature-scope filter.
Audit AI customization overlays for duplicates, conflicts, and enforceability; emit a structured scored report. Use when the user asks to review or audit customization files, or invokes /review-ai-customization-files. Requires user-provided file, list, folder, or glob.
Synchronize Markdown documentation with current code and configuration behavior. Use when the user asks to sync docs, update README after code changes, or invokes /review-and-sync-docs. Optional: scope, folder path, or feature-area filter.
Bidirectional audit of code against instruction/rule overlays and overlay coverage against the codebase. Use when the user asks to review code against instructions, check instruction coverage, or invokes /review-code-against-instructions. Optional: target path, module, file, or glob.
Review external AI output as non-authoritative input and decide safe adopt/adapt/reject actions. Use when the user pastes another model's feedback, plan, code, or prompt text, or invokes /review-other-ai-feedback. Requires the raw external output.
Analyze logs and exceptions, identify verified root causes, and plan permanent fixes. Use when the user provides error logs, stack traces, or terminal failures, or invokes /root-cause-analysis. Requires diagnostic input.
Plan what to build by reading project rules and writing ADR files. Use when starting a new Spring Boot feature, re-evaluating a plan after reviewer failures, or invoking /spring-architect. Optional input: the feature request or existing ADR path.
Implement files defined in an ADR plan by following project rules. Use when creating or fixing files as directed by the architect's plan, or invoking /spring-coder. Requires an ADR path (and optional verifier or reviewer issues).
Create or update README.md based only on files produced by the current pipeline run. Use when all reviewers have passed and the pipeline is complete, or when invoking /spring-documenter. Requires the created/modified file list.
Analyze pipeline-run outputs to identify root causes and suggest improvements to skills or project rules. Use after any pipeline completion or iteration cap exceeded, or when invoking /spring-meta-optimizer. Requires pipeline session evidence.
Main entry point for the governed Spring Boot development pipeline. Orchestrates architect, verifier, coder, reviewers, documenter, and meta-optimizer in a loop. Use when implementing a new feature, creating or modifying files, running the full development cycle, or invoking /spring-orchestrator.
Database reviewer that validates created or modified files against project rules mapped to the database review topic. Use when reviewing repository, schema, or JDBC-first data access after implementation, or invoking /spring-review-database. Requires the ADR path and the created/modified file list.
I18n reviewer that validates created or modified files against project rules mapped to the i18n review topic. Use when reviewing message keys, locale behavior, or i18n compliance after implementation, or invoking /spring-review-i18n. Requires the ADR path and the created/modified file list.
Performance reviewer that validates created or modified files against project rules mapped to the performance review topic. Use when reviewing pagination, async processing, or performance compliance after implementation, or invoking /spring-review-performance. Requires the ADR path and the created/modified file list.
QA reviewer that validates created or modified files against project rules mapped to the qa review topic. Use when reviewing code quality and compliance after implementation, or invoking /spring-review-qa. Requires the ADR path and the created/modified file list.
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.
★not rated 1 12d agoA47 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: