read-issue
Skill0 starsChanged 32 days agoMITView on GitHub
Read a GitHub issue's title, body and every comment as one CommonMark document, each in a fenced code block under its own heading.
In this repository33 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- authoritative-text-rulesSkill
- breachreaperSkill
- bug-to-contractSkill
- code-review-gateSkill
- codex-contract-test-reviewSkill
- codex-plan-reviewSkill
- codex-reviewSkill
- copilot-reviewSkill
- debtreaperSkill
- diff-rootSkill
- docreaperSkill
- done-checkSkill
- driftreaperSkill
- file-adrSkill
- file-issueSkill
- file-pubdocSkill
- file-pullreqSkill
- finding-to-auditSkill
- finding-triageSkill
- gate-miss-to-issueSkill
- gh-body-auditSkill
- gh-body-conventionsSkill
- implementSkill
- land-via-integration-branchSkill
- quality-listSkill
- reimreSkill
- research-and-implementSkill
- researchSkill
- review-pipelineSkill
- review-telemetrySkill
- stage-commit-pushSkill
- todo-checkSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
When the script cannot read its filter file or gh cannot read the issue, the script exits nonzero, prints the failing command's message on …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Read Issue
Invocation
"${CLAUDE_SKILL_DIR}/scripts/read-issue.sh" <number> [--repo OWNER/REPO]Output
A CommonMark document whose headings hold only fixed text, logins and timestamps. Everything written in the issue sits in a fenced code block:
# issue.## title, then the title in a fenced code block with the info stringtext.## body, then the body in a fenced code block with the info stringmarkdown.- For each comment,
## comment by <login> at <timestamp>, then the comment in a fenced code block with the info stringmarkdown.
Each fence is a run of backticks whose length is the larger of three and one more than the longest run of backticks in its content, so no line of the content closes it. The content inside a fence is printed unchanged.
Failure
When the script cannot read its filter file or gh cannot read the issue, the script exits nonzero, prints the failing command's message on stderr, and prints nothing on stdout.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.