code-formatter
Installation
SKILL.md
Code Formatter
When to Use
- After making code edits and before running linters/tests or opening a PR.
Rules
- Prefer
go fmt ./...for Go files; do not perform sweeping reformatting unless requested. - Only format files you changed unless the user asks for a global reformat.
- Run
gofmt/goimportswhere appropriate and include updated imports in the patch.
Commands
- Format:
go fmt ./...(orgofmt -w .when explicitly requested) - Verify:
golangci-lint run --timeout 5m --verbose ./...after formatting
Output
- Files formatted: list of changed files.
- Next: recommended lint or test command.
Related Skills
patch-applier,linter-runner
Related skills
More from pilinux/gorest
file-reader
Precisely read source files or snippets and return concise, citation-backed facts needed for decisions or edits.
26code-navigation
Rapid, focused navigation to locate definitions/usages and map the impact of proposed changes.
7fix-suggester
Diagnose failures and propose minimal, test-backed fixes with verification and rollback instructions.
7build-run
Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.
7logs-repro-harness
Reduce flaky or environment-dependent failures to a minimal, reproducible script and capture the exact logs and error lines.
7ci-orchestrator
Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.
6