.agents/skills/lint/SKILL.md
Lint all changed Go files, fix every error, and confirm the build passes. Use when the user says "fix lint", "run lint", "lint", or when pre-commit hooks fail. Also use this proactively before committing code or when you notice linter warnings in build output.
npx skillsauth add blaxel-ai/toolkit lintInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
git diff --name-only HEAD
git diff --name-only --cached
Determine which Go packages are affected so you know where to focus fixes.
make lint
This runs golangci-lint run. Capture the full output -- you need the exact errors and file locations to fix them.
Common issues and how to fix them:
if err != nil handlingDo NOT run golangci-lint run --fix -- it only auto-fixes a handful of things and misses most issues. Read the errors and fix them manually in the code.
After all fixes, re-run make lint to confirm zero errors.
If errors persist, fix them and re-run again. Do not stop until the linter passes cleanly.
go build ./...
Linter fixes can sometimes break compilation (e.g., removing an import that was actually used elsewhere). This step catches that.
Summarize what was fixed:
tools
Build the CLI in development mode. Use when the user says "build", "build dev", "compile", "rebuild", or when you need to test local changes to the CLI binary. Also use this after writing code changes to verify they compile correctly, or when the user wants to try out their changes locally.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.