skillsaw-issuelisted
Install: claude install-skill stbenjam/skillsaw
# skillsaw Issue
Use this skill when skillsaw itself needs a GitHub issue: a false positive, a
missed violation, a crash, incorrect autofix, an edge case in rule detection,
or a request for enhancement (RFE). Do not use it to report a problem in the
repository being linted unless that problem demonstrates incorrect skillsaw
behavior or a useful feature gap.
## Gather safe evidence first
Collect the minimum evidence needed to explain the issue without sending
anything externally:
- skillsaw version and the exact command
- affected rule ID, file type, and relevant configuration
- expected behavior and actual behavior for a bug
- user goal and proposed outcome for an RFE
- a minimal reproducer or a short sanitized excerpt
Never copy credentials, private repository content, or complete diagnostic
output into an issue draft. Prefer a minimal synthetic reproducer.
## Require separate permission for each external action
Ask the user two explicit questions before taking either action:
1. "May I run `skillsaw feedback` to create a local diagnostic ZIP?"
2. "May I open an issue in `stbenjam/skillsaw`?"
Do not run `skillsaw feedback` without permission for the first action. Do
not create a GitHub issue without permission for the second action. Permission
for one action does not authorize the other. If permission is absent, present
a sanitized draft and ask for the missing approval.
## Create a feedback bundle only when approved
Run `skillsaw feedback <repository-path>` with a