mcaf-formatting

Apply repository-defined formatter and linting commands to changed code.

52|6|Updated Dec 1, 2025

Search Tags:#automation #formatting #code-quality #coding-standards #agents.md #lint #repo-tools

Ready to run

npx skills add https://github.com/managedcode/MCAF --skill mcaf-formatting

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formats code to align with the repository's canonical formatting and linting commands, reducing drift and saving time spent on manual style enforcement.

Core Features & Use Cases

Applies the repo-defined formatter to changed code to ensure consistent style across the project.
Validates changes by running the repo's build/tests to catch regressions early.
Suitable for post-change cleanup and ongoing maintenance to keep diffs minimal and meaningful.

Quick Start

Run the repository’s canonical formatting command on the smallest scope possible and review the resulting diff.

Frequently Asked Questions about mcaf-formatting

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

FAQPage Schema

How do I automate code formatting across my repository?▼

Automate code formatting by running the repository's canonical formatter and linting commands defined in AGENTS.md. This ensures consistent style across the project and reduces manual formatting drift.

How do I ensure my code changes only contain formatting updates?▼

To ensure code changes are formatting-only, apply the repo-defined formatter to the smallest scope possible and review the resulting diff before committing. This keeps diffs minimal and meaningful.

Do I need an AGENTS.md file to enforce coding standards in my repo?▼

Yes, you need an AGENTS.md file to define the canonical formatting and linting commands. The Skill relies on this file to apply repo-wide coding standards and validate changes.

What is the best way to catch regressions after applying code formatting?▼

Catch regressions after code formatting by running the repository's build and tests. This validates that the formatting changes do not introduce functional errors or break existing logic.

When should I run lint and formatting commands during development?▼

Run lint and formatting commands during post-change cleanup and ongoing maintenance. Apply them when changes are introduced or when formatting drift is detected to maintain coding standards.

Why does my code formatting command not work without repository tooling?▼

Code formatting requires the repository tooling to be present because the Skill uses the repo's canonical formatter. Without these tools defined in AGENTS.md, automated formatting cannot execute.