Skip to content

hoavdc/CodexKit / skills/codexkit-test-hardening

codexkit-test-hardening

Unverified

Strengthen test coverage around changed behavior, edge cases, and regressions without writing noisy or brittle tests.

Test Hardening

Use this skill when code changes are underway or just landed and you need tests that actually protect behavior.

Focus areas

  • changed execution paths
  • high-risk conditionals
  • error handling
  • serialization or contract boundaries
  • regressions that can silently return

Workflow

  1. Identify the behavior that must remain true.
  2. Choose the narrowest test level that can protect it.
  3. Cover happy path, failure path, and one realistic edge.
  4. Verify tests fail before the fix when possible.
  5. Keep fixtures readable and cheap to maintain.

Avoid

  • snapshot-heavy tests with weak intent
  • restating implementation details instead of behavior
  • adding e2e coverage when a unit or integration test is enough

Quality Criteria

  • Every finding is tied to a specific evidence source (log, test, metric)
  • Pass/fail criteria are binary and measurable — no subjective judgments
  • Severity levels are assigned with clear thresholds
  • Remediation steps are provided for all critical and high findings

Verification (4C)

CheckQuestion
CorrectnessAre all pass/fail criteria applied against the correct standard or rule?
CompletenessWere all required dimensions or checklist items evaluated?
Context-fitDoes the verification scope match the actual risk level of the deliverable?
ConsequenceIf this passed verification but had a hidden flaw, what is the worst-case impact?

Edge Cases

  • Incomplete data for full assessment — Document which checks were limited and flag for re-verification when data becomes available.
  • Ambiguous pass/fail criteria — Request clarification from the standard owner before scoring. Mark as 'Needs Review'.
  • Multiple overlapping standards — Identify the governing standard and note where others diverge.

Changelog

  • v1.0.0 — Initial release
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 318kUpdated Claude CodeCodexUnverifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 318kUpdated Claude CodeCodexUnverifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 318kUpdated Claude CodeCodexUnverifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 196kUpdated Claude CodeCodexVerifiedInstall