finalize

Run full test suites and cross-phase acceptance checks before merge.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/n0rvyn/indie-toolkit --skill finalize-n0rvyn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finalize
Source: https://github.com/n0rvyn/indie-toolkit/tree/main/dev-workflow/skills/finalize
Command: npx skills add https://github.com/n0rvyn/indie-toolkit --skill finalize-n0rvyn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures multi-phase development work is truly complete before integration by catching failing tests, unchecked acceptance criteria, missing deliverables, and coverage gaps that per-phase checks miss.

Core Features & Use Cases

  • Precondition Validation: Detects the active dev-guide and verifies every phase has completed acceptance criteria or prompts the user to override.
  • Full Test Gate: Auto-detects and runs the project's test runner, enforces 0 failures and 0 skips, and blocks finalization on any test failures or skips.
  • Cross-Phase & Scope Verification: Parses acceptance criteria and plan files to grep for identifiers, check file deliverables, and surface regressions or scope gaps.
  • Cumulative Coverage Audit & Reporting: Aggregates plan-required tests, flags shell/missing tests, scans for untested source files relative to the dev-guide base commit, and writes a timestamped report to .claude/reviews/.
  • Use Case: Before merging a release branch, run finalize to guarantee all tests pass, acceptance criteria are satisfied or acknowledged, and coverage gaps are identified for follow-up.

Quick Start

Run the finalize skill to execute the full test suite, verify acceptance criteria and deliverables across phases, audit cumulative coverage, and write the final report to .claude/reviews/.

Frequently Asked Questions about finalize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce zero test failures and skips before merging a multi-phase development branch?

To enforce zero test failures and skips before merging, you need a final validation gate that runs the full test suite and blocks integration on any errors. This process auto-detects your project's test runner and executes all tests.

What is cross-phase acceptance criteria validation in software engineering?

Cross-phase acceptance criteria validation is the process of parsing development plan files to verify that every phase has completed its required deliverables. It surfaces regressions and scope gaps that individual per-phase checks often miss.

How do I check cumulative test coverage against a base commit before finalizing a release?

To check cumulative test coverage against a base commit, you can run a coverage audit that aggregates plan-required tests, flags missing tests, and scans for untested source files relative to the dev-guide base commit.

Can I generate a timestamped test coverage report for my development guides?

Yes, you can generate a timestamped test coverage report by running a final validation gate that audits cumulative coverage and writes the results directly to the .claude/reviews/ directory for follow-up analysis.

Does the finalize validation gate work with my project's existing test runner?

The validation gate works with your existing test runner by auto-detecting the project type to choose the appropriate execution command. It requires projects organized by dev-guides with phases including acceptance criteria and plan files.

What happens if some acceptance criteria are unchecked when running a full test gate?

If some acceptance criteria are unchecked, the full test gate will prompt the user to override the missing requirements. It verifies that every phase has completed its acceptance criteria before allowing finalization to proceed.