mcaf-formatting

Format code using repository canonical formatter and linter commands.

20|Updated Feb 1, 2026

Search Tags:#automation #workflow #linting #formatting #repository #standards #code-quality

Ready to run

npx skills add https://github.com/Zendevve/opentweak --skill mcaf-formatting-zendevve

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcaf-formatting
Source: https://github.com/Zendevve/opentweak/tree/main/.codex/skills/mcaf-formatting
Command: npx skills add https://github.com/Zendevve/opentweak --skill mcaf-formatting-zendevve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain consistent code style by applying the repository's canonical formatting and lint commands, reducing drift after changes.

Core Features & Use Cases

Automated formatting: Run the repository's standard formatter and linter to standardize code across the project.
Drift remediation: Detect and fix formatting drift introduced during edits to keep diffs minimal.
Use Case: After implementing changes or when review highlights style inconsistencies, apply the formatting pass to ensure a clean, compliant diff.

Quick Start

Run the canonical format command from AGENTS.md to reformat the touched files.

Frequently Asked Questions about mcaf-formatting

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

FAQPage Schema

How do I automatically format code to match repository standards before commits?▼

To format code to repository standards automatically, run the canonical format command defined in AGENTS.md to reformat all touched files. This enforces consistent style across the project and remediates drift introduced during edits.

What is code formatting drift and how do I fix it during code reviews?▼

Code formatting drift is style inconsistency introduced during edits. Fix it during code reviews by running the repository's canonical formatter and linter steps to detect and correct drift, ensuring a clean and compliant diff.

Does automated formatting work without configuring linter commands in AGENTS.md?▼

No, automated formatting relies on the canonical formatter and linter steps explicitly defined in the repository's AGENTS.md file. It uses these predefined commands to apply formatting and enforce consistent code style across the project.

When do I need to run linting and formatting on my code changes?▼

Run linting and formatting after implementing changes or when a review highlights style inconsistencies. Applying this formatting pass ensures the changes meet repository standards and produce a clean diff.

What's the best way to enforce code quality standards across a repository?▼

The best way to enforce code quality is by applying the repository's canonical formatter and linter commands to all code changes. This automated workflow ensures consistent style and reduces formatting drift across the project.