MC

mcaf-formatting

Automates code formatting and linting using established repository commands to ensure consistent code style.

Install

mkdir -p .claude/skills/mcaf-formatting && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12515" && unzip -o skill.zip -d .claude/skills/mcaf-formatting && rm skill.zip

Installs to .claude/skills/mcaf-formatting

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Format code and keep style consistent using the repository’s canonical formatting/lint commands from `AGENTS.md`. Use after implementing changes or when formatting drift causes noisy diffs; keep formatting changes intentional and verified with build/tests.
256 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Beginner

Key capabilities

  • Execute repository-defined formatting commands
  • Run linters on code changes
  • Review diffs for formatting-only changes
  • Verify formatting with build/tests
  • Fix `AGENTS.md` if formatter/linter commands are missing

How it works

The skill applies canonical formatting and linting commands defined in `AGENTS.md` to code, ensuring style consistency and verifying changes with build/tests.

Inputs & outputs

You give it
Code changes
You get back
Formatted code changes consistent with repository style and evidence of commands run

When to use mcaf-formatting

  • Formatting code after changes
  • Fixing linting errors
  • Ensuring consistent style in pull requests

About this skill

MCAF: Formatting

Outputs

  • Formatted code changes (consistent with repo style)
  • Evidence: formatting command(s) run and any follow-up build/tests

Workflow

  1. Use the canonical format command from AGENTS.md (do not invent commands).
  2. Run the formatter on the smallest scope possible (if your tools allow it).
  3. Review the diff:
    • ensure changes are formatting-only
    • if the formatter touched many files, separate the change or confirm it was explicitly requested
  4. Verify (follow AGENTS.md for sequencing + required commands):
    • for formatting-only changes: run the smallest meaningful verification the repo requires (build/tests/analyze as applicable)
    • for formatting as part of a behaviour change: follow the repo’s normal order (don’t reorder the pipeline)
  5. If format/linters are missing or flaky:
    • fix AGENTS.md to point to a real, repeatable command
    • only then rerun formatting
  6. Report what was run and what changed.

Guardrails

  • Do not introduce unrelated refactors under the cover of formatting.
  • Keep formatting changes and behaviour changes reviewable.

When not to use it

  • When introducing unrelated refactors
  • When formatting changes are not explicitly requested
  • When the repository does not define canonical formatting commands

Limitations

  • It relies on `AGENTS.md` for canonical commands
  • It requires the repository's formatter/linter tools
  • It does not introduce unrelated refactors

How it compares

This skill enforces repository-specific formatting rules and verifies changes through a defined workflow, preventing formatting drift and noisy diffs.

Compared to similar skills

mcaf-formatting side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
mcaf-formatting (this skill)06moNo flagsBeginner
resolve-conflicts818moReviewIntermediate
claude-automation-recommender472moReviewBeginner
codex-skill125moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

resolve-conflicts

antinomyhq

Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.

81334

claude-automation-recommender

anthropics

Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.

47140

codex-skill

feiskyer

Use when user asks to leverage codex, gpt-5, or gpt-5.1 to implement something (usually implement a plan or feature designed by Claude). Provides non-interactive automation mode for hands-off task execution without approval prompts.

12110

git-advanced-workflows

wshobson

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

1197

subagent-driven-development

davila7

Use when executing implementation plans with independent tasks in the current session

1493

validate-openapi-specs

epieczko

Validates and registers hook manifest files (YAML) in the Hook Registry for versioned hook management.

594

Search skills

Search the agent skills registry