phase-test-gate

Defines the mandatory test-gate convention for phased execution plans — every phase must end with a [TEST] step that acts as a hard gate before the next phase…

Skill by MoltenRuby

IndexedMIT

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/moltenruby-phase-test-gate

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Defines the mandatory test-gate convention for phased execution plans — every phase must end with a [TEST] step that acts as a hard gate before the next phase may begin, including exact format and acceptance rules

Use cases: testing

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/phase-test-gate

What's inside

Skill name: phase-test-gate
Description: Defines the mandatory test-gate convention for phased execution plans — every phase must end with a [TEST] step that acts as a hard gate before the next phase may begin, including exact format and acceptance rules
License: MIT
Compatibility: opencode
Instructions: 37 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

## Phase test gate convention

Every phased execution plan must include a mandatory test step at the end of each phase. This is a hard gate: the next phase must not begin until the current phase's test step passes.

### Mandatory test step rules

The last step in every phase must be:

- **Labelled** `[TEST]` at the start of its title.
- **Scoped** to the additions and changes made in that phase only — do not re-test prior phases.
- **Explicit** about what to run: list the exact commands, test files, coverage targets, or manual verification procedures.
- **A hard gate**: if it fails, the phase is incomplete and the next phase must not begin.

### Test step format

```
Step {Phase}-{N}: [TEST] {title}
Files: {test files and any supporting scripts}
Description: {Exact commands to run and what "pass" looks like.}
Acceptance: All listed commands exit with code 0 (or stated equivalents) and no test is skipped or suppressed.
```

### What counts as passing

- All listed commands exit with code 0.
- No test is marked skipped or suppressed without explicit prior agreement.
- No linter errors are introduced by the phase's changes.
- If a coverage target was specified in the requirements, it is met.

### What to do when a test step fails

1. Do not proceed to the next phase.
2. Report which assertion or command failed, with the exact error output.
3. Identify which step in the current phase is the likely cause.
4. Fix the failing step, re-run the test gate, and confirm it passes before continuing.

From MoltenRuby/MrSmith, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Mar 21, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/MoltenRuby/MrSmith
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from MoltenRuby

Cite this page

phase-test-gate skill. Agent Mart. https://agentmart.dev/skills/moltenruby-phase-test-gate (last updated 2026-10-24)