Test suite forge

Skill vishnujchandran/.agents/skills/test-suite-forge

Production-grade test suite engineering skill that designs and builds stack-aware unit, integration, contract, and end-to-end tests with CI gates, flake controls, and risk-weighted coverage targets.From its SKILL.md

Install

npx -y skills add vishnujchandran/.agents --skill test-suite-forge

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.8 KB, 833 tokens by cl100k_base, as published. Nobody here has run it

test-suite-forge (v2.0)

Build an industry-ready test system tailored to the repo’s architecture and risk profile.

Trigger Signals

Use when user asks to:

create a complete test suite for a project
harden weak or flaky tests
make tests CI/release ready
add regression protection before shipping

Modes

audit-plan (default): maturity audit + prioritized backlog
scaffold-core: add foundational test structure and starter tests
harden-existing: improve reliability/coverage/speed of existing suites

Inputs

target scope (changed-files, module, full-repo)
release criticality (low/medium/high)
current CI constraints (runtime budget, required gates)

Phase 1 — Discovery (Required)

Detect language/framework/package manager/test tooling.
Inspect current tests, coverage setup, and CI workflows.
Map critical flows: auth, permissions, writes, money, external integrations.
Build risk map by module (business impact × defect likelihood).

Phase 2 — Strategy Design

Create a project-specific test pyramid:

Unit: deterministic business logic and utility behavior
Integration: service + repository + DB boundaries
Contract/API: schema/status/error contract guarantees
E2E: smallest set of critical user journeys

Target ratio (adjust per stack):

Unit: 60–75%
Integration: 20–30%
Contract/E2E: 5–15%

Phase 3 — Generation Standards

All generated tests must follow:

Deterministic execution (time/random/network control)
Clear setup/teardown and isolated state
Reusable builders/factories over brittle fixtures
Assertions on behavior, not implementation details
Regression tests for prior defects and high-risk paths
Permission/security test cases on sensitive endpoints
Stable naming and readable test intent

Phase 4 — CI/Release Hardening

Enforce:

Fast lane and full lane test commands
Parallel-ready configuration
Coverage reporting in CI
Flaky test detection/quarantine policy
Gate policy for merge/release

Recommended gates:

PR gate: unit + integration + changed-path tests
Main gate: full suite + coverage + contract checks

Coverage & Reliability Targets

Risk-weighted targets (not vanity):

Critical paths: >= 90% branch coverage
Core services/APIs: >= 80% line + branch coverage
Repository baseline: >= 70% then ratchet up

Track additionally:

suite runtime budget
flaky test rate
escaped defects

Output Contract

Return exactly:

Test maturity summary (current vs target)
Tooling recommendation (only if required)
Test architecture map
Prioritized backlog (P0/P1/P2 | area | test type | reason)
Generated/updated test files
CI commands + gate policy
Remaining risks + next improvements

Fail Conditions

Mark as not-release-ready if:

critical flows lack regression coverage
flaky rate is unresolved on critical suites
no enforceable CI gate exists for required paths

Framework Mapping (Use existing stack first)

JS/TS: Vitest/Jest + Testing Library + Playwright/Cypress + Supertest
Python: pytest + pytest-cov + requests/httpx + Playwright
Go: testing + testify + httptest + testcontainers
Java: JUnit 5 + Mockito + Spring Test + RestAssured
.NET: xUnit/NUnit + FluentAssertions + WebApplicationFactory

Templates

Use:

templates/test-backlog-template.md
templates/ci-gate-template.md

Guardrails

Never claim pass status unless tests were run
Prefer additive minimal diffs over wholesale rewrites
Avoid unnecessary tool churn
Keep suites maintainable for the team operating them

What ships with it: 2 files

406 B alongside SKILL.md

templates/

ci-gate-template.md234 B
test-backlog-template.md172 B

Gives 0 of the 12 instructions most test skills give in 833 tokens

Counted across 964 of the 1,571 authors here whose files we hold, read 2026-08-07

Close the browser when donein 55 of 964, across 12 files
Wait for network idle statein 51 of 964, across 6 files
Launch Chromium in headless modein 49 of 964, across 6 files
Use descriptive selectors for elementsin 49 of 964, across 6 files
Run provided scripts with help flag firstin 49 of 964, across 6 files
Add appropriate explicit waitsin 48 of 964, across 5 files
Use bundled scripts as black boxesin 46 of 964, across 3 files
Do not read script source codein 46 of 964, across 3 files
Use sync playwright for scriptsin 46 of 964, across 3 files
Inspect dom before executing actionsin 46 of 964, across 3 files
Run the full test suitein 37 of 964
Write the failing test firstin 29 of 964, across 23 files

Said here and by no other author read

map critical flows and integrations
build a module risk map
create a project specific test pyramid
add regression tests for high risk paths
enforce fast lane and full lane tests
enforce a flaky test quarantine policy

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.