checkpoint

Run all quality gates and audit agents, then output phase reports in Markdown and JSON.

2|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/chieflatif/vibeos-plugin --skill checkpoint-chieflatif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/chieflatif/vibeos-plugin/tree/main/plugins/vibeos/skills/checkpoint
Command: npx skills add https://github.com/chieflatif/vibeos-plugin --skill checkpoint-chieflatif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase-based software projects rely on consistent quality checks at phase boundaries. This skill runs all gates and audit agents across the entire codebase to establish baselines and enforce ratcheting, preventing regression in quality from one phase to the next.

Core Features & Use Cases

  • Run all quality gates on the full codebase at the end of a phase to verify adherence to standards.
  • Dispatch the 8 audit agents in a coordinated cycle, aggregate findings, and apply consensus logic.
  • Load the previous baseline, compare results, and generate a phase report that highlights ratchet outcomes and recommended actions.

Quick Start

Run a phase checkpoint for phase 3 to evaluate the current codebase against the prior baseline.

Frequently Asked Questions about checkpoint

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

FAQPage Schema
How do I enforce code quality gates at phase boundaries to prevent regression?

Ratchet decisions in baseline comparison lock in improvements by refusing new violations, ensuring code quality never degrades from one phase boundary to the next.

How do I run a phase checkpoint to audit codebase quality against a previous baseline?

Yes, baseline comparison loads the prior phase baseline from .vibeos/baselines/phase-[N-1]-baseline.json, compares current audit findings, and generates a phase-wide report highlighting ratchet outcomes.

Can I scale phase-boundary quality control to audit a large codebase?

The phase checkpoint dispatches 8 audit agents in a coordinated cycle, aggregates their findings, and applies consensus logic to generate a comprehensive phase-wide report of gate results.

What is the best way to generate a phase-wide quality report with ratchet outcomes?

The phase report outputs in both Markdown and JSON forms, detailing gate results, audit findings, and ratchet decisions to provide a complete phase-boundary quality assessment.

Do I need a prior baseline file to perform a phase checkpoint?

No external dependencies are required, but the checkpoint requires the prior baseline file at .vibeos/baselines/phase-[N-1]-baseline.json to execute baseline comparison and ratchet decisions.