@boyingliu01/xp-gate 0.7.0 → 0.8.0

package/plugins/claude-code/skills/test-driven-development/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: test-driven-development
+description: >
+  Test-Driven Development enforcement: RED → GREEN → REFACTOR cycle.
+  Write failing test first, then minimum code to pass, then refactor.
+  Includes Mock Usage Guidelines for integration-first testing.
+
+maturity: stable
+---
+
+# Test-Driven Development
+
+## Core Principles
+
+| Principle | Description |
+|-----------|-------------|
+| **RED First** | Write a failing test before ANY implementation code |
+| **GREEN Minimum** | Write minimum code to pass the test — no extra features |
+| **REFACTOR** | Clean up code while keeping tests green |
+| **Delete & Restart** | If you write code before test — delete it and start over |
+
+## Workflow
+
+```
+1. RED: Write failing test (describe/it + expect)
+2. GREEN: Write minimum implementation to pass
+3. REFACTOR: Clean up, extract, simplify — tests stay green
+4. Repeat for next behavior
+```
+
+## Mock Usage Guidelines (MANDATORY)
+
+### When to use mocks (ONLY these cases):
+1. External API/HTTP calls — use testcontainers or nock
+2. Database I/O — use in-memory DB (sqlite, testcontainers)
+3. File system I/O — use tmpdir / memfs
+4. Time-dependent code — inject clock dependency
+5. Non-deterministic behavior (random, UUID) — inject dependency
+
+### When NOT to use mocks:
+- Pure business logic → test with real values
+- In-memory data transformations → test with real data
+- Validation logic → test with real input/output
+- State machines → test with real state transitions
+
+### Mock Density Rule:
+If > 30% of test lines contain mock/spy/fn references,
+you are likely over-mocking. Add `// @mock-justified: <reason>` comment
+explaining why integration test is not feasible.
+
+### Annotation Format:
+```typescript
+// @mock-justified: external API wrapper, no sandbox environment available
+```
+Reason text must be at least 10 characters. Bare `@mock-justified` without colon+reason is invalid.
+
+## Test Annotations
+
+```typescript
+/**
+ * @test REQ-XXX Feature name
+ * @intent Verify specific behavior
+ * @covers AC-XXX-01, AC-XXX-02
+ */
+```
+
+## Coverage Requirements
+
+- Minimum 80% line coverage
+- All acceptance criteria must have corresponding tests
+- Tests must survive mutation testing (Gate M pre-push)

package/plugins/claude-code/skills/test-specification-alignment/AGENTS.md

@@ -0,0 +1,56 @@
+# SKILLS/TEST-SPECIFICATION-ALIGNMENT KNOWLEDGE BASE
+
+**Generated:** 2026-05-30
+**Commit:** 4517f2b
+**Branch:** main
+**Version:** v0.5.1
+
+## OVERVIEW
+Test-Specification Alignment Engine — two-stage validation ensuring tests accurately reflect requirements and design specs.
+
+## STRUCTURE
+```
+skills/test-specification-alignment/
+├── SKILL.md              # Core alignment workflow (2-phase)
+├── AGENTS.md             # This file
+├── evals/                # Evaluation test cases
+└── references/           # Supporting documentation
+```
+
+## WHERE TO LOOK
+| Task | Location | Notes |
+|------|----------|-------|
+| Core workflow | SKILL.md | Phase 1 (align) + Phase 2 (execute) |
+| Freeze mechanism | SKILL.md | Prevents test modifications during Phase 2 |
+
+## CONVENTIONS
+- Phase 1 (Align): test modifications ALLOWED to align with specification
+- Phase 2 (Execute): test modifications FORBIDDEN (freeze enforced)
+- Minimum 80% alignment score required to pass
+- All `@test`, `@intent`, `@covers` JSDoc tags mandatory in test files
+- Test annotations trace to REQ-XXX and AC-XXX
+
+## ANTI-PATTERNS (THIS PROJECT)
+- Do NOT modify tests during Phase 2 execution
+- Do NOT proceed with low alignment score (<80%)
+- Do NOT skip specification validation if specification exists
+- Do NOT delete test files in Phase 2 (freeze intercepts)
+- Do NOT modify assertions when tests fail (modify business code instead)
+- Missing @test tags → test rejected
+
+## UNIQUE STYLES
+- Two-phase separation (modify vs. execute)
+- Freeze/unfreeze test protection mechanism
+- YAML specification-driven validation (specification.yaml)
+- Structured JSDoc tag requirements (@test, @intent, @covers)
+
+## COMMANDS
+```bash
+/test-specification-alignment   # Run alignment check
+```
+
+## NOTES
+- Runs during BUILD (Phase 2) after TDD
+- Mandatory before gstack-ship release
+- Integrates with test-driven-development skill
+- Uses freeze skill to lock test directories during Phase 2