| name | skill-intake |
| disable-model-invocation | true |
| description | Move incoming issues and pull requests through triage states until each is actionable or closed — use when the queue has piled up or a report arrives unsorted |
Intake
Work the incoming queue. Each item moves through a small set of states until it
is either actionable by someone who did not write it, or closed with a reason.
A pull request is an issue with attached code. Same states, same moves, with
the deltas noted below. Resolving a bare #42 means checking both.
Adapted from triage in
mattpocock/skills (MIT), cut down to the
states this repo can actually represent and retargeted at gh and bd.
When To Use
- Open issues or PRs have accumulated and nobody knows which are real.
- A new report arrives and needs sorting before anyone works it.
- An issue has been sitting because it is not clear what it is asking for.
- Before planning, to establish what is actually in the queue.
When Not To Use
- To do the work an item describes. Triage decides what happens to it, not how.
- For local, private notes. That is
skill-issues and .octo/ISSUES.md.
- To review a PR's code quality. That is
skill-code-review or
skill-staged-review; intake decides whether the PR should be reviewed at all.
Inputs
An issue or PR reference, or nothing — with nothing, take the queue in order.
and for the public surface; and
for tracked work.