Close blank issues and route requests by kind

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>

.changeset/github-tracker-own-repo.md

@@ -0,0 +1,5 @@
+---
+"mattpocock-skills": patch
+---
+
+The GitHub issue tracker template that `setup-matt-pocock-skills` writes now tells agents to file issues only into the user's own repo, never into `mattpocock/skills`, and to check the target repo before the first `gh issue create`. Agents working in a clone or fork of this repo had filed their specs and tickets here (#541 to #550).

.github/ISSUE_TEMPLATE/bug.yml

@@ -1,10 +1,12 @@
 name: Bug
-description: A skill did the wrong thing in a real session.
-labels: ["bug"]
+description: A skill did the wrong thing in a real session. One bug per issue.
+labels: [bug, needs-triage]
 body:
   - type: markdown
     attributes:
       value: |
+        Keep it short and put the repro first. If an agent wrote this for you, cut it down to the repro before you post. See [CONTRIBUTING.md](https://github.com/mattpocock/skills/blob/main/CONTRIBUTING.md).
+
         Bugs in `skills/misc/` are not fixed (see [`.out-of-scope/frozen-misc-skills.md`](https://github.com/mattpocock/skills/blob/main/.out-of-scope/frozen-misc-skills.md)). Installer problems with `npx skills` belong at skills.sh.
   - type: input
     id: skill
@@ -13,11 +15,19 @@ body:
       description: Which skill, e.g. `to-tickets`, `grilling`.
     validations:
       required: true
+  - type: input
+    id: version
+    attributes:
+      label: Version or commit
+      description: The plugin version, or the commit SHA you installed from. Many bugs are already fixed on `main`.
+      placeholder: 1.3.1, or 4588b32
+    validations:
+      required: true
   - type: input
     id: harness
     attributes:
       label: Harness and version
-      description: e.g. Claude Code 2.3.1, Codex CLI 0.40, Cursor. Say how you installed (plugin or skills.sh) and which skills version.
+      description: e.g. Claude Code 2.3.1, Codex CLI 0.40, Cursor. Say how you installed (plugin or skills.sh).
     validations:
       required: true
   - type: input
@@ -31,7 +41,7 @@ body:
     id: what-happened
     attributes:
       label: What happened
-      description: What you ran, and what the skill did. Paste the relevant part of the session.
+      description: The smallest steps that show the bug, and what the skill did. Paste the relevant part of the session.
     validations:
       required: true
   - type: textarea
@@ -41,3 +51,12 @@ body:
       description: What the skill should have done instead, and which line of the SKILL.md (if any) says so.
     validations:
       required: true
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Checks
+      options:
+        - label: This issue is about one problem.
+          required: true
+        - label: I searched open and closed issues for a duplicate.
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,14 @@
 blank_issues_enabled: false
 contact_links:
-  - name: Questions and discussion
-    url: https://github.com/mattpocock/skills/discussions
-    about: How-do-I questions, ideas you want to talk through, and anything that isn't a concrete failure in a skill.
+  - name: Question or "how do I...?"
+    url: https://github.com/mattpocock/skills/discussions/categories/q-a
+    about: Ask in Q&A. Issues are for bugs and changes to existing skills only.
+  - name: New skill idea, or a skill you want to donate
+    url: https://github.com/mattpocock/skills/discussions/categories/ideas
+    about: Post it in Ideas. New skills do not start as issues.
+  - name: Support for another harness or issue tracker
+    url: https://github.com/mattpocock/skills/discussions/categories/ideas
+    about: Post it in Ideas. Read the out-of-scope notes first, most trackers are already ruled out.
+  - name: Is my request out of scope?
+    url: https://github.com/mattpocock/skills/blob/main/SCOPE.md
+    about: The bar every issue must clear, and the requests this repo has already decided not to take.

.github/ISSUE_TEMPLATE/idea.yml

@@ -1,5 +1,6 @@
 name: Idea or feedback
-description: A change to an existing skill, grounded in a failure you saw.
+description: A change to an existing skill, grounded in a failure you saw. One change per issue.
+labels: [enhancement, needs-triage]
 body:
   - type: markdown
     attributes:
@@ -17,6 +18,10 @@ body:
       options:
         - label: I've read `SCOPE.md` and checked `.out-of-scope/`, and this isn't covered by either.
           required: true
+        - label: This issue is about one problem.
+          required: true
+        - label: I searched open and closed issues for a duplicate.
+          required: true
   - type: input
     id: skill
     attributes:
@@ -35,6 +40,6 @@ body:
     id: change
     attributes:
       label: Proposed change
-      description: What you'd change in the skill, as concretely as you can.
+      description: The smallest change that fixes it. Describe it; don't paste a rewritten SKILL.md.
     validations:
       required: true

CONTRIBUTING.md

@@ -0,0 +1,25 @@
+# Contributing
+
+Every issue is judged against the bar in [`SCOPE.md`](./SCOPE.md). Read it first.
+
+## Where each request goes
+
+| You have | Go to |
+| --- | --- |
+| A bug in a skill | [Bug issue](https://github.com/mattpocock/skills/issues/new?template=bug.yml) |
+| A change to an existing skill | [Idea or feedback issue](https://github.com/mattpocock/skills/issues/new?template=idea.yml) |
+| A question, or "how do I...?" | [Discussions: Q&A](https://github.com/mattpocock/skills/discussions/categories/q-a) |
+| An idea for a new skill, or a skill to donate | [Discussions: Ideas](https://github.com/mattpocock/skills/discussions/categories/ideas) |
+| Support for another harness or issue tracker | [Discussions: Ideas](https://github.com/mattpocock/skills/discussions/categories/ideas), after you read [`.out-of-scope/`](./.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.md` files. 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-skills` in your project.

skills/engineering/setup-matt-pocock-skills/issue-tracker-github.md

@@ -16,6 +16,8 @@ Issues and specs for this repo live as GitHub issues. Use the `gh` CLI for all o
 
 Infer the repo from `git remote -v`; `gh` does this automatically when run inside a clone.
 
+File issues only into the user's own repo. Never file into `mattpocock/skills` (the repo these skills come from) unless the user owns it. In a fork, `gh` can default to the upstream parent, so before the first `gh issue create` of a session, check the target with `gh repo view --json nameWithOwner` and confirm it with the user if it is not their repo.
+
 ## Pull requests as a triage surface
 
 **PRs as a request surface: no.** _(Set to `yes` if this repo treats external PRs as feature requests; `/triage` reads this flag.)_