Agent skill

Validate Tests

by gittower in gittower/git-flow-next

Codex-gate the test plan in an implementation plan before implementation starts

Custom licenceAuto-check: notesTesting & QA

Install Validate Tests

skills CLI
$ npx skills add gittower/git-flow-next --skill validate-tests -a claude-code

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

GitHub CLI
$ gh skill install gittower/git-flow-next validate-tests --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/gittower/git-flow-next.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/validate-tests .claude/skills/validate-tests && 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
validate-tests
GitHub stars
458
Token cost
~660 tokens
SKILL.md length
312 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
Custom licence

At a glance

Codex-gate the test plan in an implementation plan before implementation starts

  • Works in 5 steps: Find the Plan → Local Validation → Codex Gate → …
  • Tasks that involve Test generation
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Planning

What it does

Validate Tests is an agent skill from gittower/git-flow-next. Codex-gate the test plan in an implementation plan before implementation starts

Its SKILL.md is about 660 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test generation and Planning. It works with Git. The repository describes itself as: A modern reimplementation of git-flow in Go that offers greater flexibility while maintaining backward compatibility with the original git-flow and git-flow-avh.

When your agent uses it

  • Tasks that involve Test generation
  • Tasks that involve Planning

Example prompts

  • “/validate-tests”

Requirements

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

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Find the Plan
  2. Local Validation
  3. Codex Gate
  4. Evaluate and Apply
  5. Report Findings

What it can do on your machine

Read from SKILL.md and the folder at commit 00d1b4b. 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
    • Edit
    • Write
    • Bash
    • Agent

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Validate Tests loads about 660 tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 312 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~660

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, Edit, Write, Bash, Agent

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 312 words (~660 tokens).

“Gate the test plan of an implementation plan before any implementation starts. Combines a local check against the testing guidelines with an external Codex review, following the shared convention in ../_shared/CODEX_GATE.md.”

— opening of SKILL.md by gittower, Custom licence
name
validate-tests
allowed-tools
Read, Grep, Glob, Edit, Write, Bash, Agent

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/validate-tests of gittower/git-flow-next.

Open the folder on GitHubat commit 00d1b4b

Compare with similar skills

Validate Tests 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.

Validate Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Validate Tests this skillgittower/git-flow-next458—~660Automated safety check: NotesCustom licence
Specifying Mbd Algorithmsmatlab/simulink-agentic-toolkit1.2k—~1.9kAutomated safety check: PassCustom licence
Test RoadmapOvid/paad131—~2.3kAutomated safety check: PassMIT
Verify Changesh0x91b/dev-3.0307—~1.7kAutomated safety check: PassApache-2.0
Codexqa Testcase Generatoropenqa-cn/codexqa152—~3.6kAutomated safety check: PassMIT
Git Facade Test Conventionsruby-git/ruby-git1.8k—~4.2kAutomated safety check: PassMIT

Similar skills

  • Specifying Mbd Algorithms

    matlab/simulink-agentic-toolkit

    Specify algorithms for Model-Based Design: system specs, architecture specs, implementation plans, test plans.

    1.2k GitHub stars~1.9k tokensUpdated 6 days ago
    Testing & QAAuto-check passed
  • Test Roadmap

    Ovid/paad

    EXPERIMENTAL. An agent skill from Ovid/paad.

    131 GitHub stars~2.3k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Verify Changes

    h0x91b/dev-3.0

    How to test and verify work in the dev-3.0 repo — which vitest config covers what, how to write a test that fits the house style, mocking Electrobun RPC and i18n providers, what coverage is actually…

    307 GitHub stars~1.7k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Generates test plans and test cases from local requirements for APP, Web, and server.

    152 GitHub stars~3.6k tokensUpdated 4 days ago
    Testing & QAAuto-check passed
  • Conventions for writing and reviewing unit and integration tests of Git::Repository facade methods in the ruby-git project, covering setup, cases, grouping and scope.

    1.8k GitHub stars~4.2k tokensUpdated 5 days ago
    Testing & QAAuto-check passed
  • Base Comparison

    stylelint-stylistic/stylelint-stylistic

    Measure a branch against the commit it stands on — extract the base instead of flipping the working tree, pick the base by hash, and prove a new test case red on it.

    106 GitHub stars~2.2k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from gittower/git-flow-next

All 25 skills in this repo
  • GitHub Issue Analysis

    gittower/git-flow-next

    Analyzes a GitHub issue for the git-flow-next project and writes an analysis document under .ai/ that covers the affected code and proposes TODO comments.

    458 GitHub starsUsed in 1 repo~694 tokens
    Auto-check: notes
  • PR Review Feedback Handler

    gittower/git-flow-next

    Fetches review comments on a pull request, judges each one, writes the evaluation to a plan file and implements accepted changes, waiting for approval before anything public.

    458 GitHub stars~2.9k tokensUpdated 29 days ago
    Auto-check: notes
  • Stale PR Review Check

    gittower/git-flow-next

    Scans open pull requests against the project's review response window and reports which ones need action, read-only unless you approve a reminder.

    458 GitHub stars~549 tokensUpdated 29 days ago
    Auto-check: notes
  • Local Code Review

    gittower/git-flow-next

    Reviews local commits, branch diffs or pull requests against project guidelines and writes the result to local files, never posting it to GitHub.

    458 GitHub stars~1.9k tokensUpdated 29 days ago
    Auto-check: notes
  • Commit with Project Guidelines

    gittower/git-flow-next

    Creates a commit that follows the project's COMMIT_GUIDELINES.md, choosing the type by what the change does and verifying the result.

    458 GitHub stars~818 tokensUpdated 29 days ago
    Auto-check: notes
  • Test-First Implementation Plan

    gittower/git-flow-next

    Builds a two-phase implementation plan from a spec issue, analysis or concept, writing a detailed test plan first and the implementation outline second.

    458 GitHub stars~1.3k tokensUpdated 29 days ago
    Auto-check: notes

Works with

Questions about Validate Tests

What does Validate Tests do?

Codex-gate the test plan in an implementation plan before implementation starts. Validate Tests is an agent skill from gittower/git-flow-next.

When should I use Validate Tests?

Validate Tests fits situations like: tasks that involve Test generation; tasks that involve Planning.

How do I install Validate Tests in Claude Code?

Run `npx skills add gittower/git-flow-next --skill validate-tests -a claude-code`. Or copy the skill folder (.claude/skills/validate-tests in gittower/git-flow-next) into .claude/skills/validate-tests in your project. Claude Code loads it when a task matches its description.

How do I install Validate Tests in Codex?

Run `npx skills add gittower/git-flow-next --skill validate-tests -a codex`. Or copy the skill folder (.claude/skills/validate-tests in gittower/git-flow-next) into .agents/skills/validate-tests in your project. Codex loads it when a task matches its description.

Can I use Validate Tests 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 gittower/git-flow-next --skill validate-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/validate-tests, .gemini/skills/validate-tests, .github/skills/validate-tests and .opencode/skills/validate-tests in your project.

What does Validate Tests need to run?

SKILL.md names no scripts, command-line tools or credentials: Validate Tests is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, Edit, Write, Bash, Agent.

Does Validate Tests 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 Validate Tests 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 Validate Tests use?

Validate Tests has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Validate Tests use?

About 660 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Validate Tests?

Skills that share tags, products or a category with Validate Tests: Specifying Mbd Algorithms (matlab/simulink-agentic-toolkit, 1.2k stars), Test Roadmap (Ovid/paad, 131 stars), Verify Changes (h0x91b/dev-3.0, 307 stars) and Codexqa Testcase Generator (openqa-cn/codexqa, 152 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Validate Tests?

gittower (a GitHub organization) maintains it in gittower/git-flow-next, which has 458 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on September 8, 2026.

Source: gittower/git-flow-next on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.