code-format

Runs language-specific formatters and linters across Python, Go, YAML, shell, and Helm source files.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/witwave-ai/witwave --skill code-format-witwave-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-format
Source: https://github.com/witwave-ai/witwave/tree/main/.agents/self/nova/.claude/skills/code-format
Command: npx skills add https://github.com/witwave-ai/witwave --skill code-format-witwave-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a multi-language repository consistently formatted requires running many different tools with the right file sets, configs, and commit hygiene. This Skill automates a mechanical formatting and linting pass across the whole source tree, producing per-language commits and a durable log of diagnostics that cannot be auto-fixed. ## Core Features & Use Cases - Multi-language formatting: Runs ruff for Python, gofmt/goimports for Go, prettier for JSON/YAML/TS/Vue/TOML, and shfmt for shell scripts, honoring project-pinned configs like pyproject.toml and .prettierrc.yaml. - Diagnostic-only linting: Surfaces findings from yamllint, shellcheck, helm lint, hadolint, and actionlint without changing behavior, logging them to a persistent findings file. - Per-language commits: Groups auto-fixes into separate commits per language so the history stays readable, skipping empty change sets. - Use Case: Before a release, ask for a code format pass to normalize every tracked source file, commit the fixes per language, and receive a report of remaining lint findings for later triage. ## Quick Start Ask the agent to run a code format pass over the repository checkout and commit the formatter fixes per language.

Frequently Asked Questions about code-format

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

FAQPage Schema
How do I format Python, Go, and YAML files in one pass?▼

Run a code format pass that enumerates tracked files with git ls-files and applies each language's formatter: ruff format for Python, gofmt and goimports for Go, and prettier for JSON, YAML, TOML, TypeScript, and Vue. Fixes are committed separately per language.

What is the difference between ruff format and ruff check --fix?▼

ruff format mechanically reformats Python code style, while ruff check --fix applies safe lint auto-fixes such as removing unused imports. A final ruff check without --fix reports remaining diagnostics that need manual attention.

Does this formatting pass modify Markdown or generated code?▼

No. Markdown is explicitly excluded because documentation formatting is owned by a separate docs-validate workflow, and generated or vendored code such as zz_generated files and vendor directories is filtered out of the file lists.

Can shellcheck, hadolint, or actionlint auto-fix issues?▼

No. shellcheck, hadolint, and actionlint are diagnostic-only tools, so their findings are logged to a findings file with rule IDs and line numbers rather than being fixed automatically. Only shfmt auto-fixes shell script formatting.

What happens if a formatter like prettier or helm is not installed?▼

The pass checks tool availability first and logs a tooling-missing entry for any absent formatter, then skips only that language's pass. All other languages still run so the run produces partial value.