skillsaw-lintlisted
Install: claude install-skill stbenjam/skillsaw
# skillsaw Lint
You just authored or edited agentic context — a skill, slash command, agent,
hook, plugin, marketplace, or instruction file (CLAUDE.md, AGENTS.md,
GEMINI.md, Cursor/Copilot/Cline/Kiro rules), or the configuration that
loads it (an OpenCode `opencode.json`). That content feeds an agent's
context window, and defects in it — weak language, contradictions,
placeholder text, instructions buried in attention dead zones — degrade
every future session that loads it. Lint it with **skillsaw** and improve
it before you report the work as done.
Run the skillsaw CLI for every step below; it is the interface for linting,
fixing, and explaining — replace any hand-rolled check with it.
## Step 1: Locate skillsaw
Run `skillsaw --version`. If the command is missing, check the project for a
pinned version before installing — look in the Makefile, pyproject.toml, or
an existing `.venv` (e.g. `.venv/bin/skillsaw --version`). Use that version
with `uvx skillsaw==<version>` as the prefix for every command below (or
`pip install skillsaw==<version>` if uvx is unavailable).
## Step 2: Lint what you wrote
Run the linter scoped to the files or directories you created or edited:
```sh
skillsaw lint <path>
```
Read each violation line: it carries the severity, file path, line number,
message, and rule ID. If the repository defines its own lint entry point (a
Makefile `lint` target that runs skillsaw, for example), run that instead —
it may pin a version or pass flags like `--stri