implement

Run per-commit review, implementation, verification, and critique workflows.

4|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/alexanderguy/skills --skill implement-alexanderguy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/alexanderguy/skills/tree/main/skills/implement
Command: npx skills add https://github.com/alexanderguy/skills --skill implement-alexanderguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incomplete or poorly designed changes by forcing every commit through an architectural review, a full build/test gate, and a scoped critique loop.

Core Features & Use Cases

  • Greybeard approach review per commit: Aligns on intent, trade-offs, and expected file impact before any code is written.
  • Test-aware implementation discipline: Uses test-first guidance for bug fixes and test-backed verification for new features, matching repo conventions.
  • Hard build gate before committing: Runs the full pipeline (format, lint, build, test or equivalent) and blocks commits on failures caused by your changes.
  • Critique loop with amend/rebase workflow: Iteratively fixes findings using git commit --amend or git rebase -i edit stops until Critique is clean.

Quick Start

Load the implement skill and follow its per-commit workflow to produce each commit with Greybeard review, passing build gate, and a verified Critique loop.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I enforce a build gate and architectural review before every git commit?

You can enforce a build gate and architectural review before every git commit by running a per-commit workflow that blocks commits on format, lint, build, or test failures, and requires an architectural approach review to align on trade-offs before writing code.

What is a critique loop in a git commit workflow?

A critique loop in a git commit workflow is an iterative process that fixes code review findings using git commit --amend or git rebase -i edit stops, repeating until the critique returns clean and verified results.

How do I split implementation sessions into commit-sized units with explicit boundaries?

To split implementation sessions into commit-sized units, apply a per-commit workflow that tracks progress through architectural review, test-aware implementation, a full build gate, and a critique loop for each scoped change.

Does this per-commit review workflow require specific test conventions to run?

Yes, the per-commit review workflow requires repo test conventions to function, using test-first guidance for bug fixes and test-backed verification for new features to satisfy the hard build gate before committing.

Why should I run a full build and test pipeline before committing code changes?

You should run a full build and test pipeline before committing code changes to prevent incomplete or poorly designed changes from entering your repository, ensuring every commit passes format, lint, build, and test gates.