mirror of
https://github.com/mattpocock/skills.git
synced 2026-11-06 05:17:24 +00:00
Matt PocockandClaude Opus 5.5
59db609eb1
Add issue forms (bug, change to an existing skill) with a one-problem and duplicate-search check, turn off blank issues, and send questions, new-skill ideas and other harness or tracker requests to Discussions. Add a short CONTRIBUTING.md with the rules for AI-written issues. Tell the GitHub issue tracker template to file only into the user's own repo, never into mattpocock/skills, which is how #541 to #550 landed here. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
1.5 KiB
1.5 KiB
Contributing
Every issue is judged against the bar in SCOPE.md. Read it first.
Where each request goes
| You have | Go to |
|---|---|
| A bug in a skill | Bug issue |
| A change to an existing skill | Idea or feedback issue |
| A question, or "how do I...?" | Discussions: Q&A |
| An idea for a new skill, or a skill to donate | Discussions: Ideas |
| Support for another harness or issue tracker | Discussions: Ideas, after you read .out-of-scope/ |
Pull requests are open to collaborators only, so describe the fix in an issue instead.
Issues written with AI
Agents are welcome to help, but you post the issue, so you own it:
- One problem per issue. Several findings from one session are several issues, or none.
- Short. If it does not fit on one screen, cut it.
- Repro first. The steps that show the problem come before any analysis.
- No pasted specs. No full proposals, plans, or rewritten
SKILL.mdfiles. Describe the problem; the fix is ours to design. - Not your project's issues. If your agent files the specs or tickets for your own project here, it has the wrong repo. Run
/setup-matt-pocock-skillsin your project.