Claude-skill-registry-data mcaf-formatting

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.

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry-data

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry-data "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/mcaf-formatting" ~/.claude/skills/majiayu000-claude-skill-registry-data-mcaf-formatting && rm -rf "$T"

manifest: data/mcaf-formatting/SKILL.md

source content

MCAF: Formatting

Outputs

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

Workflow

Use the canonical
```
format
```
command from
```
AGENTS.md
```
(do not invent commands).
Run the formatter on the smallest scope possible (if your tools allow it).
Review the diff:
- ensure changes are formatting-only
- if the formatter touched many files, separate the change or confirm it was explicitly requested
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)
If
```
format
```
/linters are missing or flaky:
- fix
```
AGENTS.md
```
  to point to a real, repeatable command
- only then rerun formatting
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.