integrate

Run the full project test suite and record the binding verdict.

5|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/friedbotstudio/baseline --skill integrate-friedbotstudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integrate
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/integrate
Command: npx skills add https://github.com/friedbotstudio/baseline --skill integrate-friedbotstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps the integration phase disciplined by running the full test suite, recording the binding verdict, and stopping the workflow when verification fails. It prevents premature documentation or commit steps until the project has passed the required checks.

Core Features & Use Cases

  • Full-suite verification: Executes the project test command from the configured baseline and applies strict pass or fail verdict rules.
  • Workflow state management: Updates workflow completion state, writes the test result file, and sets the harness state so the automation can continue or yield correctly.
  • Optional cross-engine smoke checks: When the project includes a supported browser setup and frontend surface, it can run browser smoke validation and surface advisory findings for review.
  • Use case: A developer finishes a feature branch and uses this Skill to confirm the entire suite passes before the repository advances to documentation or commit preparation.

Quick Start

Use the integrate skill to run the full project test suite, record the verdict, and advance the workflow only if verification succeeds.

Frequently Asked Questions about integrate

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

FAQPage Schema
How do I gate releases using deterministic integration testing?

To gate releases with deterministic integration, execute your full project test suite and apply strict pass or fail verdict rules. The workflow only advances to documentation or commit preparation when verification succeeds, preventing premature releases.

How does test suite verification manage workflow state?

Workflow state management records the binding verdict by updating completion state, writing the test result file, and setting the harness state. This coordinates continue-or-yield behavior for automation without requiring code changes or subagent delegation.

Can I run cross-engine smoke testing for frontend targets?

Yes, cross-engine smoke testing is supported for frontend targets. When a project includes a supported browser setup and frontend surface, it executes browser smoke validation and surfaces advisory findings for review during the integration phase.

Do I need strict last_test_result formatting for integration verification?

Yes, strict last_test_result formatting is required. The integration verification process depends on precise formatting and harness_state coordination to correctly stamp the binding verdict and determine whether the workflow should continue or yield.

Why does my workflow stop when test suite verification fails?

The workflow stops when test suite verification fails to maintain integration phase discipline. By recording the binding verdict and halting on failure, it ensures no premature documentation or commit steps proceed until the project passes all required checks.

What is the best way to validate prerequisites before committing a feature branch?

The best way to validate prerequisites before committing a feature branch is running full-suite verification. This executes the project test command from the configured baseline, applying deterministic state updates and strict pass or fail verdict rules before advancing.