unit-test-project-conformant

Unit Test (Project-Conformant) Skill

This skill ensures the agent does not invent test structure and instead learns how the project already tests similar code, then writes the new test in the same style, location, and pattern.

The goal is for the new test to be indistinguishable from existing tests.

When to Use

• Use this skill every time a unit test must be written or modified.
• Use this skill when adding coverage for new functions, classes, or behavior.
• Use this skill when refactoring code that requires corresponding test updates.
• This skill is required whenever the agent is tempted to create a “clean” or “ideal” test structure.

Instructions

Step 1 — Discover How the project Tests Similar Code

Before writing any test:

• Identify the file, function, or class to be tested.
• Search the project for tests covering:
  • The same module
  • The same directory
  • Similar functions
  • Similar classes
  • Similar behavior
• Use search terms such as:
  • Function name
  • Class name
  • Module name
  • Error messages
  • Public API names

You must examine at least 2–3 similar tests before proceeding.

---

Step 2 — Extract the Test Pattern

From the discovered tests, learn:

• Where tests are located
• File naming conventions
• Test naming conventions
• Whether tests are:
  • Standalone functions
  • Inside classes
  • Parametrized
  • Fixture-driven
  • Integration-style
• Assertion style
• Mocking style
• Helper utilities used
• What is intentionally not tested

You are learning the project’s testing contract.

---

Step 3 — Decide Where the Test Belongs

Follow existing structure exactly:

• If similar code is tested in a shared file → add to that file
• If similar code is tested inside a class → add a method there
• If similar tests extend parametrization → extend it
• If similar behavior is only tested indirectly → do the same

Do not create a new test file unless similar tests do.

---

Step 4 — Match Style Exactly