certify-work

Certifies uncommitted changes or commit ranges through a review-fix loop before commit.

1|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/fallguyconsulting/ok-plugins --skill certify-work-fallguyconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: certify-work
Source: https://github.com/fallguyconsulting/ok-plugins/tree/main/plugins/ok/ceremonies/certify-work
Command: npx skills add https://github.com/fallguyconsulting/ok-plugins --skill certify-work-fallguyconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams need a consistent, change-scoped quality gate that reviews and fixes defects in work just completed before it is archived or committed, without relying on ad-hoc manual review. ## Core Features & Use Cases - Change-scoped certification: Reviews the uncommitted working tree by default, or a specified git commit range, deriving the changed-file set once for all stages. - Review-fix loop: Runs code review producers, a fixer, and an architect in rounds until no findings remain open and no files were edited, with a cap as a thrash guard. - Family-aware orchestration: Detects which skill families (ok-planner, ok-plumbline, ok-workspaces) are present via filesystem estate checks and folds in each family's ceremony contribution. - Use Case: After finishing a sprint's implementation work, run the gate to have every defect in the diff found, fixed, and presented, with archival and commit offered as owner-approved closing acts. ## Quick Start Invoke the /certify-work slash command to certify the uncommitted working tree through the review-fix loop.

Frequently Asked Questions about certify-work

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

FAQPage Schema
How do I certify uncommitted changes before committing?▼

Run the /certify-work slash command with no arguments. It scopes the review to the uncommitted working tree using git status and git diff, then runs producers and a review-fix loop until no findings remain open.

How do I review a specific git commit range for defects?▼

Pass a git range or ref as an argument, such as main..HEAD or abc123..def456. The gate then certifies that range's diff plus the uncommitted tree, deriving the changed-file set from the combined diff.

What happens when the review finds defects in my change?▼

Every finding enters a review-fix loop: a fixer task edits the required files, and an architect handles kickbacks, refutations, and reversals. Rounds repeat until a round makes no edits and no finding stands open, or a cap stops the run.

Does certify-work work without the ok-planner estate installed?▼

No. The ok-planner estate is required because it vendors the shared certification core, the task tracker at .ok-planner/bin/tasks, and the agent profiles. Without them, the gate reports the missing pieces and stops.

When should I use audit instead of certify-work?▼

Use the whole-corpus audit verb before a release, after a run of sprints, or when you need to know whether a corpus's claims still hold. Certify-work is scoped to a single change and never audits the wider corpus.