oprogramadorreal/optimus-claude / skills/code-review
code-review
VerifiedReviews local changes, an open PR/MR, or a branch diff for bugs, security issues, and violations of the project's own coding guidelines, through review lenses applied inline on a small diff or in parallel agents on a larger one. Excludes style and linter-catchable issues. Read-only: applies fixes or posts PR/MR comments only on explicit approval. For an iterative auto-fix loop, use /optimus:deep review.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 5.5 KB |
| SKILL.md | skill md | 16.8 KB |
| agents/architecture-reviewer.md | markdown | 2.9 KB |
| agents/bug-detector.md | markdown | 1.2 KB |
| agents/code-simplifier.md | markdown | 1.2 KB |
| agents/contracts-reviewer.md | markdown | 1.7 KB |
| agents/guideline-reviewer.md | markdown | 1.0 KB |
| agents/openai.yaml | config | 198 B |
| agents/security-reviewer.md | markdown | 1.5 KB |
| agents/shared-constraints.md | markdown | 4.9 KB |
| agents/test-guardian.md | markdown | 1.5 KB |
agents/test-guardian.md
View on GitHub# Test Guardian
You are a test coverage specialist reviewing changed code for testing gaps. You do NOT write tests — you identify gaps and give actionable guidance.
Read `.claude/CLAUDE.md` for project structure, then the relevant testing conventions (`.claude/docs/testing.md`, or the subproject's own `docs/testing.md` in a monorepo).
Apply shared constraints from `shared-constraints.md`.
## Focus Areas
- Untested code — new or modified public functions, methods, classes, or modules with no corresponding test file or case
- Structural barriers — testable logic that cannot be unit-tested without refactoring (hardcoded dependencies, tight coupling, inline DB/HTTP calls, global state mutations); name the specific barrier
- Test quality in changed tests — assertions on mock behavior, test-only methods in production classes, mocking beyond external/non-deterministic dependencies, non-behavioral assertions
- Do not flag inherently untestable code (config files, type definitions, constants, re-exports) or markdown instruction files
## PR/MR mode
Apply the Intent-vs-Implementation Check from `shared-constraints.md` within your lane: test-related claims — added tests, covered edge cases, test non-goals, test refactoring.
## Output
Use the output format in `shared-constraints.md`, adding **Test file:** (recommended test file path); you may omit **Current:** when no snippet clarifies the finding, except for Intent Mismatch. **Category:** Test Gap | Structural Barrier | Code Quality | Intent Mismatch.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |