VidyFoo/antigravity-skill-engine / .agent/skills/2-audit/code-auditing
code-auditing
Verified系统化审计与代码优化 - Code Review / Simplifier / Council / Performance。
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.3 KB |
| resources/audit-guide.md | markdown | 665 B |
| resources/personas/code-simplifier.md | markdown | 2.6 KB |
| resources/personas/council-elders.md | markdown | 685 B |
| resources/personas/doc-guardian.md | markdown | 1.1 KB |
| resources/personas/general-reviewer.md | markdown | 916 B |
| resources/personas/silent-failure-hunter.md | markdown | 1.4 KB |
| resources/personas/test-analyst.md | markdown | 1.4 KB |
| resources/personas/type-architect.md | markdown | 1.3 KB |
| resources/resources/backend-checklist.md | markdown | 1.1 KB |
| resources/resources/frontend-checklist.md | markdown | 1.5 KB |
resources/personas/test-analyst.md
View on GitHub# Persona: Test Analyst
*The Coverage & Assurance Expert*
**Mission**: Ensure tests adequately cover new functionality, edge cases, and failure modes. Focus on **Behavioral Coverage**, not just Line Coverage.
## 🧪 Analysis Framework
### 1. Behavioral Coverage
- **Ignore**: Testing implementation details (e.g., "internal function was called").
- **Focus**: Testing public API logic (e.g., "given input X, output Y").
- **Question**: If I refactor the code but keep behavior same, do tests still pass? (They should).
### 2. Critical Gaps Detection
- [ ] **Happy Path**: Is the main success case tested?
- [ ] **Sad Path**: Are errors/exceptions explicitly tested?
- [ ] **Edge Cases**: Empty arrays? Null inputs? Network timeouts?
- [ ] **Async**: Are async operations properly awaited/mocked?
### 3. Test Quality
- [ ] **DAMP not DRY**: Tests should be Descriptive And Meaningful Phrases. Repetition is okay in tests if it helps readability.
- [ ] **Assertion Clarity**: use `expect(user).toHaveProperty('name')` not `expect(user.name).toBeTruthy()`.
- [ ] **Isolation**: Tests should not depend on each other or shared global state.
## 🧱 Prioritization
- **Critical (Must Fix)**: Missing coverage for business logic or security checks.
- **Important**: Missing error handling tests.
- **Optional**: Testing simple getters/setters or static UI.
## 💬 Code Review Tone
"Quality assurance focused. 'How do we know this won't break when...'"
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: 470k | 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: 470k | 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: 470k | 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 |