← ClaudeAtlas

skillsaw-create-pluginlisted

Create a skillsaw rule plugin — a pip-installable Python package that adds custom lint rules to skillsaw. Walks through scaffolding the package, writing rules against the lint tree, testing, and publishing to PyPI. Use when a user wants to share skillsaw rules across repositories or publish them for others.
stbenjam/skillsaw · ★ 73 · AI & Automation · score 90
Install: claude install-skill stbenjam/skillsaw
# skillsaw Create Plugin Create a **skillsaw rule plugin**: a Python package that adds lint rules to [skillsaw](https://skillsaw.org). Once you build and publish to PyPI, anyone can `pip install` it and skillsaw picks up the rules automatically — no config required. Prefer this to per-repo `custom-rules:` files when sharing rules across repos. Keep the terminology straight: a *skillsaw plugin* adds rules to the skillsaw linter itself. Never confuse it with the Claude Code plugins that skillsaw lints. Review this reference material while you work: - Read the plugin guide: https://skillsaw.org/plugins/ - Follow the rule-writing guide (lint tree, block types): https://skillsaw.org/custom-rules/ and https://skillsaw.org/lint-tree/ - Read the complete working example: `examples/plugins/skillsaw-example-plugin/` in the [skillsaw repo](https://github.com/stbenjam/skillsaw) Follow each step in order, and keep the user updated on progress at each stage. ## Step 1: Gather requirements Review the following with the user: 1. **What should each rule check?** Get concrete examples of content that should pass and content that should fail. 2. **Rule IDs** — use kebab-case, descriptive (e.g. `no-todo-instructions`). Run `skillsaw list-rules` and confirm no ID collides with a builtin rule or another installed plugin; skillsaw never loads colliding plugin rules. 3. **Severity** — set each rule to `error` (must fix), `warning` (should fix), or `info` (advisory). 4. **Package name**