Agent Claude Code
An independent code-review and testing role for Java projects. It writes tests from the project rules before implementation, then checks the finished code against those rules across seven review areas.
135 tagged java, measured the same way as everything else here.
Browse within: spring-boot 28angular 26github-copilot 17langchain4j 16code-quality 15jenkins 15linter 15python 15terraform 15go 14spec-driven-development 12tdd 12hexagonal-architecture 11llm-agent 11
Agent Claude Code
An independent code-review and testing role for Java projects. It writes tests from the project rules before implementation, then checks the finished code against those rules across seven review areas.
loiane/specs-driven-development-spring-angular
Agent Claude Code
Phase 4 (red step) — write the failing frontend test for each Angular task before any production code. Use when running /build for frontend tasks.
loiane/specs-driven-development-spring-angular
Agent Claude Code
Bootstrap an existing Spring codebase into the spec-driven workflow. Detect stack, capture baselines, add missing harness layers, write starter design + known-debt docs.
loiane/specs-driven-development-spring-angular
Agent Claude Code
Phase 6 — run the harness, parse every report, build the traceability matrix, emit a deterministic verdict in 07-validation-report.md and 07a-traceability.md.
Agent Claude Code
Runs this repository's Maven verification for a change — the full build, one module, one test, the two-phase doc check, coverage or mutation testing — and reports the verdict with only the output that explains a failure. Use when a change needs checking and the whole build log would otherwise land in the conversation.
Agent Claude Code
Reads CLAUDE.md, AGENTS.md, README.md and the poms together and reports the facts that have drifted apart but that no enforcer rule pins — counts, catalogue tables, command lists, module descriptions. Use after adding a module, skill, rule, MCP tool or profile, and before a release.
Agent Claude Code
Review code/config changes and keep all docs fresh across three altitudes — internal docs (docs/DESIGN.md WHAT/WHY, docs/ARCHITECTURE.md HOW), operator docs in docs/ (CONFIGURATION, CLI, AGENT-GUIDE, CODEBASEREQUIREMENTS, MANUAL-VERIFICATION-CHECKLIST), and the consumer skills/ + agents/ artifacts deployed verbatim to…
Agent
MUST BE USED PROACTIVELY. Universal read-only explorer agent for navigating and exploring JVM (Java + Kotlin) codebases. Combines graph navigation via the jrag CLI (call chains, routes, service boundaries, clients, producers, impact, FQN resolution) with jrag search (locate code/config by meaning, keywords, or natural…
Agent
MUST BE USED PROACTIVELY. Universal read-only explorer agent. Combines jrag graph navigation (call chains, service boundaries, routes, impact analysis, FQN resolution) with broad file-system search (grep, glob, excerpt reading). Use for any exploration task: locating code, tracing dependencies, finding patterns…
Agent Claude Code
Issues product owner. Validate implementation against feature catalog and feature/.md definitions; find gaps, stale docs, and missing happy paths. Suggest backlog ideas. Use when reviewing product completeness, catalog compliance, or prioritizing new capabilities.
Agent Claude Code
Issues security auditor. Review code for authz, authn, injection, secrets, and XSS/CSRF risks; write a findings report and teach developers how to fix each issue via remediation tasks. Use for security audits — not for implementing patches. Prefer over generic review when the user asks for security issues or a full…
Agent Claude Code
TDD Red phase for Issues. Create a failing test only — no production code. Use when starting TDD, adding behaviour, or user asks for a failing test first.
Agent Claude Code
Audit dependencies for CVEs and outdated versions. Use for security checks or before releases.
Agent Claude Code
Compare jhelm template output against Go Helm for a specific chart. Use to verify rendering compatibility.
Agent Claude Code
Review code changes against jhelm project standards. Use when reviewing PRs or before creating one.
Agent
Stage 2 of two-stage review. Spec compliance already verified by Stage 1. Reviews security, performance, maintainability, readability, test quality. Severity-tagged output (P0/P1/P2/P3/P4) with MANDATORY rule ID citation per finding.
Agent
Decompose chosen solution into vertical slices with dependency graph + risk register. Consumes Align + Brainstorm artifacts. Output feeds Spec gate. Use after Brainstorm gate (high-stakes) or directly after Align (standard with obvious solution).
Agent
Behavioral spec generator — translates approved plans into concrete, testable contracts. Use when /spec is invoked after plan approval.
Agent
Use this agent when you need to evaluate system design decisions, architectural patterns, and technology choices at the macro level.
Agent
Use this agent to IMPLEMENT infrastructure automation, CI/CD pipelines, containerization, and deployment workflows once the design/approach is clear. Writes and verifies actual Terraform/OpenTofu, Kubernetes manifests, Dockerfiles, and pipeline config across AWS/Azure/GCP/DigitalOcean, configures edge security…
Agent
Figma execution agent that creates, edits, and updates design files in Figma via the official Figma MCP server. Materializes UX specs and design-system conventions into Figma frames, components, auto-layout, variables, and tokens. Use AFTER @ux-designer has produced a spec (docs/work/ /solutions/) and…
Agent
Topology-aware code explorer for a fleet of multi-repo Spring Boot microservices. Traces a request or feature across service repos and shared libraries, following inter-service (proxy-lib) calls. Use when you need to understand how a flow works across more than one repo.
Agent
Computes the cross-fleet blast radius of a change to a shared-lib symbol, file, or service endpoint - returns every consumer across every service repo with file:line citations, grouped by service and consumer kind.
Agent
Reads logs across many Spring Boot services, correlates them by a trace key (e.g. sessionId), reconstructs one cross-service timeline, and isolates the failing hop. Use when debugging a runtime issue that spans services.