Agent skill

Post Dev Test

by sd0xdev in sd0xdev/sd0x-harness

Post-development test completion. An agent skill from sd0xdev/sd0x-harness.

MITAuto-check: notesTesting & QA

Install Post Dev Test

skills CLI
$ npx skills add sd0xdev/sd0x-harness --skill post-dev-test -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sd0xdev/sd0x-harness post-dev-test --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/post-dev-test .claude/skills/post-dev-test && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
post-dev-test
GitHub stars
192
Token cost
~1.8k tokens
SKILL.md length
199 words
Files
2 (incl. references)
Skills in repo
91
Repo updated
First seen
Licence
MIT

At a glance

Post-development test completion. An agent skill from sd0xdev/sd0x-harness.

  • : checking test coverage after feature-dev
  • SKILL.md covers Trigger, When to Use, Key Rule: Must Execute on… and When NOT to Use, plus 8 more sections
  • Calls yarn
  • Writing missing integration/e2e tests

What it does

Post Dev Test is an agent skill from sd0xdev/sd0x-harness. Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/test-patterns.md`).

It sits in Testing & QA, covering Test coverage, End-to-end testing and Unit testing. The repository describes itself as: The harness layer for Claude Code — a reference implementation of harness engineering with hook-enforced dual review, state-machine gates that survive context compaction, and… The licence is MIT.

When your agent uses it

  • : checking test coverage after feature-dev
  • Writing missing integration/e2e tests

Example prompts

  • “/post-dev-test”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Write, Bash

What it can do on your machine

Read from SKILL.md and the folder at commit c9a2036. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Write
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • yarn

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use yarn, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Post Dev Test loads about 1.8k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 65 tokens; SKILL.md has 199 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Glob, Write, Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sd0xdev/sd0x-harness at commit c9a2036, republished under its MIT licence (© sd0xdev). 199 words, ~1,755 tokens.

Download SKILL.mdSave it as .claude/skills/post-dev-test/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
post-dev-test
description
Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.
allowed-tools
Read, Grep, Glob, Write, Bash

Post-Dev Test Skill

Trigger

  • Keywords: add tests, integration test, e2e test, test coverage, post dev test

When to Use

  • After completing feature development, before /precommit
  • Want to ensure new features have sufficient integration/e2e coverage
  • Unit tests exist, but higher-level tests are missing

Key Rule: Must Execute on Changes

Even if test coverage looks complete, tests must be executed whenever there are code changes.

ScenarioAction
Code changes existMust execute related integration/e2e
Tests exist and are completeStill execute to confirm no regression
Tests missing or insufficientWrite then execute
Pure doc/comment changesCan skip

Reason: Test coverage does not equal tests passing. Existing tests may fail due to code changes.

When NOT to Use

  • Only need unit tests (use /codex-test-gen)
  • Review existing tests (use /codex-test-review)
  • Still in development (complete /feature-dev flow first)

Workflow

┌─────────────────────────────────────────────────────────────────┐
│ Phase 1: Analyze Context                                        │
├─────────────────────────────────────────────────────────────────┤
│ 1. From conversation history: what feature was developed?       │
│ 2. Identify involved Service / Provider / Controller            │
│ 3. List core flows and API endpoints                            │
└─────────────────────────────────────────────────────────────────┘
                              ↓
┌─────────────────────────────────────────────────────────────────┐
│ Phase 2: Check Existing Test Coverage                           │
├─────────────────────────────────────────────────────────────────┤
│ 1. Search test/integration/ for related tests                   │
│ 2. Search test/e2e/ for related tests                           │
│ 3. Assess coverage gaps                                         │
└─────────────────────────────────────────────────────────────────┘
                              ↓
┌─────────────────────────────────────────────────────────────────┐
│ Phase 3: Determine Test Strategy                                │
├─────────────────────────────────────────────────────────────────┤
│ ┌──────────────┬────────────────────────────────────────────┐   │
│ │ Change Type  │ Test Requirement                           │   │
│ ├──────────────┼────────────────────────────────────────────┤   │
│ │ New API      │ Integration test (Controller + Service)    │   │
│ │ New Service  │ Integration test (Service layer)           │   │
│ │ Cross-svc    │ E2E test (complete flow)                   │   │
│ │ DB operation │ Integration test (actual DB)               │   │
│ │ External API │ Integration test (mock external)           │   │
│ └──────────────┴────────────────────────────────────────────┘   │
└─────────────────────────────────────────────────────────────────┘
                              ↓
┌─────────────────────────────────────────────────────────────────┐
│ Phase 4: Write Tests                                            │
├─────────────────────────────────────────────────────────────────┤
│ 1. Reference existing test patterns                             │
│ 2. Use {FRAMEWORK_MOCK_LIB} createApp / createRequester        │
│ 3. Follow TEST_ENV environment variable conventions             │
│ 4. Write to corresponding directory                             │
└─────────────────────────────────────────────────────────────────┘
                              ↓
┌─────────────────────────────────────────────────────────────────┐
│ Phase 5: Execute Verification                                   │
├─────────────────────────────────────────────────────────────────┤
│ 1. Execute newly added tests                                    │
│ 2. Confirm passing                                              │
│ 3. Report results                                               │
└─────────────────────────────────────────────────────────────────┘

Test File Conventions

TypeDirectoryNamingEnv Variable
Integrationtest/integration/*.integration.test.ts or *.test.tsTEST_ENV=integration
E2Etest/e2e/*.e2e.test.ts or *.test.tsTEST_ENV=e2e

Test Template

typescript
import { Application, Framework } from '{FRAMEWORK_WEB}';
import { close, createApp } from '{FRAMEWORK_MOCK_LIB}';
import { ITestRequester, createRequester } from '../../createRequester';
import { TestEnvironment, onlyIf } from '../../helper/test-env';

const describeIntegration = onlyIf([
  TestEnvironment.INTEGRATION,
  TestEnvironment.E2E,
]);

describeIntegration('Feature Integration Tests', () => {
  let app: Application;
  let request: ITestRequester;

  beforeAll(async () => {
    app = await createApp<Framework>();
    request = await createRequester(app);
  });

  afterAll(async () => {
    await close(app);
  });

  describe('Scenario: ...', () => {
    it('should ...', async () => {
      // Arrange
      // Act
      // Assert
    });
  });
});

Output

  • Test files (integration/e2e) in correct directories
  • Coverage delta report
  • Gate: ✅ Coverage sufficient / ⛔ Gaps remaining

Verification

  • Test files in correct directory
  • Using correct TEST_ENV condition
  • Tests can run independently
  • Covers main flow + error scenarios

Execute Tests

bash
# Execute single integration test
TEST_ENV=integration yarn jest test/integration/path/to/test.ts

# Execute single e2e test
TEST_ENV=e2e yarn jest test/e2e/path/to/test.ts

Examples

Input: (User Authentication feature developed in conversation)
Phase 1: Identify ActiveAssetsWeeklyService, ActiveAssetsCacheService involved
Phase 2: Search test/e2e/auth/ -> found missing login test
Phase 3: Decide to write E2E test (cross-service flow)
Phase 4: Write active-assets-weekly.e2e.test.ts
Phase 5: Execute test and verify passing
Input: (New API endpoint developed in conversation)
Phase 1: Identify Controller + Service
Phase 2: Search test/integration/controller/ -> no corresponding test
Phase 3: Decide to write Integration test
Phase 4: Write new-feature.integration.test.ts
Phase 5: Execute test and verify passing

References

  • references/test-patterns.md - Existing test pattern reference

© sd0xdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/post-dev-test of sd0xdev/sd0x-harness.

  • SKILL.md
  • references/test-patterns.md

Open the folder on GitHubat commit c9a2036

Compare with similar skills

Post Dev Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Post Dev Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Post Dev Test this skillsd0xdev/sd0x-harness192—~1.8kAutomated safety check: NotesMIT
Atdd Mutateswingerman/engineer154—~2.7kAutomated safety check: PassMIT
Test Coverageluongnv89/skills131—~2.5kAutomated safety check: PassMIT
Scenario Testingaiskillstore/marketplace4301 repos~830Automated safety check: PassNone
Test Automationrevfactory/harness-1001.3k—~1.7kAutomated safety check: PassApache-2.0
Test Specialisttravisjneuman/.claude101—~3.7kAutomated safety check: PassMIT

Similar skills

  • Atdd Mutate

    swingerman/engineer

    A skill your agent uses to add a third validation layer to the ATDD workflow — after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies the tests actually catch bugs.

    154 GitHub stars~2.7k tokensUpdated 14 days ago
    Testing & QAAuto-check passed
  • Test Coverage

    luongnv89/skills

    Generate unit tests for untested branches and edge cases. An agent skill from luongnv89/skills.

    131 GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check passed
  • Scenario Testing

    aiskillstore/marketplace

    This skill should be used when writing tests, validating features, or needing to verify code works.

    430 GitHub starsUsed in 1 repo~830 tokens
    Testing & QAAuto-check passed
  • Test Automation

    revfactory/harness-100

    A full test automation pipeline. An agent skill from revfactory/harness-100.

    1.3k GitHub stars~1.7k tokensUpdated 6 mo ago
    Testing & QAAuto-check passed
  • Test Specialist

    travisjneuman/.claude

    Test-writing patterns for JS/TS, Python, Go, and Rust (unit, integration, E2E, visual regression).

    101 GitHub stars~3.7k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Dotnet Testing

    novotnyllc/dotnet-artisan

    Defines .NET test strategy and implementation patterns across xUnit v3 (Facts, Theories, fixtures, IAsyncLifetime), integration testing (WebApplicationFactory, Testcontainers), Aspire testing…

    233 GitHub stars~972 tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

More from sd0xdev/sd0x-harness

All 91 skills in this repo
  • Adr

    sd0xdev/sd0x-harness

    Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/<feature/adr-<NNN-<title.md with a 3-digit zero-padded…

    192 GitHub stars~4.8k tokensUpdated yesterday
    Auto-check passed
  • Load PR Review

    sd0xdev/sd0x-harness

    Load GitHub PR review comments into AI session — analyze, triage, plan.

    192 GitHub stars~4.4k tokensUpdated yesterday
    Auto-check passed
  • Next Step

    sd0xdev/sd0x-harness

    Change-aware next step advisor. An agent skill from sd0xdev/sd0x-harness.

    192 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Obsidian CLI

    sd0xdev/sd0x-harness

    Obsidian vault integration via official CLI. An agent skill from sd0xdev/sd0x-harness.

    192 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Orchestrate

    sd0xdev/sd0x-harness

    Agent-driven workflow orchestration (v1 report-only). An agent skill from sd0xdev/sd0x-harness.

    192 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • PR Comment

    sd0xdev/sd0x-harness

    Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review.

    192 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Post Dev Test

What does Post Dev Test do?

Post-development test completion. An agent skill from sd0xdev/sd0x-harness. Post Dev Test is an agent skill from sd0xdev/sd0x-harness. Post-development test completion.

When should I use Post Dev Test?

Post Dev Test fits situations like: : checking test coverage after feature-dev; writing missing integration/e2e tests.

How do I install Post Dev Test in Claude Code?

Run `npx skills add sd0xdev/sd0x-harness --skill post-dev-test -a claude-code`. Or copy the skill folder (skills/post-dev-test in sd0xdev/sd0x-harness) into .claude/skills/post-dev-test in your project. Claude Code loads it when a task matches its description.

How do I install Post Dev Test in Codex?

Run `npx skills add sd0xdev/sd0x-harness --skill post-dev-test -a codex`. Or copy the skill folder (skills/post-dev-test in sd0xdev/sd0x-harness) into .agents/skills/post-dev-test in your project. Codex loads it when a task matches its description.

Can I use Post Dev Test in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sd0xdev/sd0x-harness --skill post-dev-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/post-dev-test, .gemini/skills/post-dev-test, .github/skills/post-dev-test and .opencode/skills/post-dev-test in your project.

What does Post Dev Test need to run?

Going by SKILL.md and its folder, Post Dev Test needs the command-line tools its instructions call (yarn). Its frontmatter pre-approves these tools: Read, Grep, Glob, Write, Bash.

Does Post Dev Test access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Post Dev Test safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Post Dev Test use?

Post Dev Test is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Post Dev Test use?

About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.

What are the alternatives to Post Dev Test?

Skills that share tags, products or a category with Post Dev Test: Atdd Mutate (swingerman/engineer, 154 stars), Test Coverage (luongnv89/skills, 131 stars), Scenario Testing (aiskillstore/marketplace, 430 stars) and Test Automation (revfactory/harness-100, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Post Dev Test?

sd0xdev (a GitHub user) maintains it in sd0xdev/sd0x-harness, which has 192 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 6, 2026.

Source: sd0xdev/sd0x-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.