repo-applying-maker-checker-fixer

Coordinate maker, checker, and fixer roles for repository content validation.

3|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/wahidyankf/ose-primer --skill repo-applying-maker-checker-fixer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-applying-maker-checker-fixer
Source: https://github.com/wahidyankf/ose-primer/tree/main/.claude/skills/repo-applying-maker-checker-fixer
Command: npx skills add https://github.com/wahidyankf/ose-primer --skill repo-applying-maker-checker-fixer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates ad-hoc, unvalidated content creation and remediation workflows that lead to inconsistent documentation, agent output errors, and governance non-compliance across software repositories. It replaces manual, error-prone content review processes with a standardized, coordinated three-stage pattern that ensures all content meets defined quality standards before publication.

Core Features & Use Cases

  • Three-Stage Coordinated Workflow: Separates responsibilities across Maker (content creation/updates with full dependency management), Checker (non-destructive validation with progressive audit report generation), and Fixer (confidence-based automated remediation of validated issues) roles to eliminate overlap and gaps.
  • Prioritized Fix Execution: Combines criticality and confidence levels to prioritize fixes, with configurable mode thresholds (lax/normal/strict/ocd) to control how many issues are automatically addressed versus flagged for manual review.
  • Iteration Loop Prevention: Includes built-in safeguards like false positive tracking, scoped re-validation of only changed files, and escalation paths for unresolved disagreements to ensure checker-fixer workflows converge quickly without infinite loops.
  • Use Case: Software engineering teams managing large monorepos can use this Skill to standardize quality checks for documentation, AI agent outputs, repository governance content, and plan artifacts, reducing manual review time while ensuring consistent compliance with repository conventions.

Quick Start

Use the repo-applying-maker-checker-fixer skill to implement a coordinated three-stage content quality workflow for your repository's documentation, agent outputs, and governance content, with dedicated roles handling creation, validation, and automated remediation of verified issues.

Frequently Asked Questions about repo-applying-maker-checker-fixer

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

FAQPage Schema
What is the maker-checker-fixer workflow for repository content validation?

The maker-checker-fixer workflow is a standardized three-stage pattern for repository content validation that separates content creation, convention-based checking, and automated remediation to eliminate unvalidated content publication.

How do I prevent infinite loops between checker and fixer agents during automated remediation?

To prevent infinite loops between checker and fixer agents, use built-in safeguards like false positive tracking, scoped re-validation of only changed files, and escalation paths to ensure validation workflows converge quickly.

Can I use this workflow to validate AI agent outputs and governance content in a monorepo?

Yes, you can use the maker-checker-fixer workflow to validate AI agent outputs and governance content in a monorepo, applying coordinated role separation to ensure systematic content creation and convention-based validation.

How do I configure fix execution thresholds for automated content remediation?

Configure fix execution thresholds by combining criticality and confidence levels with mode settings like lax, normal, strict, or ocd to control how many validated issues are automatically fixed versus flagged for manual review.

What's the best way to standardize documentation quality assurance across a software repository?

The best way to standardize documentation quality assurance is implementing a three-stage maker-checker-fixer pattern that enforces progressive audit report generation and confidence-based automated fixing of verified issues.