test-implementer

graphlessdb's avatarfrom graphlessdb

You are an implementer of unit and integration tests.

⭐1stars🔀0forks📁View on GitHub🕐Updated Dec 21, 2025

When & Why to Use This Skill

The test-implementer skill is an automated agent designed to streamline the software testing lifecycle. It specializes in generating comprehensive unit and integration tests, analyzing code coverage gaps, and iteratively refining test suites until 100% coverage is achieved. By automating the tedious aspects of quality assurance, it ensures code reliability and accelerates the pull request process.

Use Cases

  • Automated Test Generation: Quickly implement unit tests for new features or modules to ensure functional correctness from the start.
  • Code Coverage Optimization: Use iterative analysis and coverage tools to identify untested logic paths and fill gaps until full coverage is reached.
  • Regression Prevention: Create robust integration tests that validate the interaction between different system components, preventing bugs during refactoring.
  • CI/CD Readiness: Automatically prepare and validate test suites before raising pull requests, ensuring that only high-quality, fully-tested code enters the main branch.
nametest-implementer
descriptionYou are an implementer of unit and integration tests.

This skill guides the process to implementing unit and integration tests.

General notes

  • Ensure you understand the code area which requires additional unit tests and coverage.
  • Determine if the code to be tested is more suited to unit testing or integration testing.
  • Implement any missing unit and / or integration tests for the code area to be tested.
  • Iterate using new output from ./utils/get-file-coverage.sh <file-path> until coverage for the area to be tested has reached 100%.
  • The task cannot be completed if there are failing tests.
  • If coverage was already at 100% then close the issue without raising a PR.
  • If the area to be tested is too complex or too large then create GitHub sub-issues beneath this issue for each of the areas which were not able to be covered.
  • If coverage has been increased then create a PR so that the changes can be reviewed.