check-work

Run lint, format, and test checks after implementation tasks.

Updated Jun 10, 2026
One-click install
npx skills add https://github.com/brewpirate/acme-frontier-ai --skill check-work-brewpirate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-work
Source: https://github.com/brewpirate/acme-frontier-ai/tree/main/catalog/skills/check-work
Command: npx skills add https://github.com/brewpirate/acme-frontier-ai --skill check-work-brewpirate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents completed work from slipping through with broken lint, formatting, tests, missing documentation, or unfinished journal updates.

Core Features & Use Cases

  • Quality Gate Verification: Runs the project's lint, format, and test checks to confirm the work is technically sound.
  • Automatic Recovery: Tries fix commands first and escalates to manual repair when issues remain.
  • Documentation and Audit Trail: Reviews changes, updates relevant docs, and records a journal entry so the work is traceable.
  • Use Case: After finishing a feature or fix, use this Skill to verify the repository is clean, complete, and ready to hand off.

Quick Start

Use the check-work skill to verify the finished changes and resolve any failing quality gates before marking the task complete.

Frequently Asked Questions about check-work

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

FAQPage Schema
How do I verify quality gates before shipping code?

To verify quality gates before shipping, run checks across linting, formatting, testing, and documentation updates. This process ensures completed work is technically sound and prevents broken code from slipping through the final review.

What is the best way to automate linting and formatting checks after implementation?

Automating linting and formatting checks involves sequentially executing project commands to validate the codebase. This skill discovers project commands automatically and applies them to confirm formatting and lint compliance after implementation tasks.

How do I automatically recover from failing test suites or broken checks?

To automatically recover from failing test suites, apply fix commands first and escalate to manual repair when issues remain. This troubleshooting method coordinates fixes across multiple files to resolve broken checks.

Why does code review require documentation and journal updates?

Code review requires documentation and journal updates to maintain a traceable audit trail. Reviewing changes and updating relevant docs ensures the repository is clean, complete, and the work is traceable before handoff.

Can I run a full test suite verification without manual intervention?

Yes, you can run full test suite verification without manual intervention by using sequential gate execution. The system attempts automatic remediation where possible and only escalates to manual repair for persistent failures.