file-issue
Skill309 starsChanged 4 months agoApache-2.0View on GitHub
File a GitHub issue for a bug or improvement found this session.
13 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Sma1lboy/rovetheir own version, first seen Nov 14, 2026
- rome-os/rometheir own version, first seen Nov 12, 2026
- pushprove-max/Commandecktheir own version, first seen Nov 8, 2026
- Termherd/termherdtheir own version, first seen Nov 8, 2026
- enes-alatas/spooltheir own version, first seen Nov 8, 2026
- ultimatile/development-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use review-pr.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
DockerSkillreview-pr
Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.
Also in 4 projects that use this
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- marin-community/marin★ 4.1k64% same
Wrote their own version · 12
- rilldata/rill★ 3ksame name
- levy-street/world-of-claudecraft★ 2.3ksame name
- rome-os/rome★ 904same name
- Sma1lboy/rove★ 187same name
- enes-alatas/spool★ 48same name
- mlz11/ClaudeNotifier★ 36same name
- pushprove-max/Commandeck★ 3same name
- bhagyamudgal/skills★ 2same name
- gssajith/claude-skills★ 2same name
- shuvamk/openbench★ 2same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analyze-datagen-campaign-summarySkill
- analyze-dataset-token-lengthSkill
- analyze-id-eval-rankingSkill
- analyze-job-history-irisSkill
- analyze-rl-behaviorSkill
- analyze-training-run-irisSkill
- build-tpu-image-irisSkill
- code-create-staged-planSkill
- code-execute-staged-planSkill
- commitSkill
- crud-archive-runSkill
- crud-otagent-supabaseSkill
- crud-purge-below-gate-evalsSkill
- crud-purge-stale-eval-placeholdersSkill
- datagen-create-task-datasetSkill
- datagen-job-cleanupSkill
- datagen-launch-irisSkill
- datagen-launchSkill
- datagen-reduce-dataset-snapshotsSkill
- datagen-standard-launchSkill
- debugSkill
- docs-deslopSkill
- eval-agentic-cleanupSkill
- eval-agentic-launch-irisSkill
- eval-agentic-launchSkill
- eval-standard-cleanupSkill
- eval-standard-launchSkill
- monitor-cron-sweep-irisSkill
- monitor-cron-sweepSkill
- monitor-job-tablesSkill
- monitor-restore-irisSkill
- monitor-restoreSkill
- monitor-restore-unifiedSkill
- rl-agentic-job-cleanupSkill
- rl-agentic-launch-irisSkill
- rl-agentic-launch-jupiterSkill
- rl-job-health-deep-diveSkill
- rl-standard-job-cleanupSkill
- rl-standard-launch-leonardoSkill
- serve-model-vibe-testSkill
- sft-cleanup-hf-onlySkill
- sft-job-cleanupSkill
- sft-launchSkill
- supervisor-initSkill
- utils-cleanup-stale-sandboxesSkill
- utils-fix-permissionsSkill
- utils-reclaim-stale-snapshotsSkill
- write-testsSkill
- writing-styleSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 13 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Create a GitHub issue in the current repository from bugs, regressions, or improvements identified in the current conversation.
- Distinctive: line 100
If it's ambiguous what to file, ask the user before proceeding.
- Distinctive: line 108
Search for existing issues first:
- Distinctive: line 114
If a match exists, tell the user and offer to comment on it instead.
- Distinctive: line 124
Body: Use the section structure for the chosen kind (see above).
- Distinctive: line 128
No filler ("I noticed...", "During our conversation...").
- Distinctive: line 129
No markdown images or tables.
- Distinctive: line 131
Keep every fact needed to understand and act on the issue.
- Very specific: line 134
Do not repeat the title in a Description section.
- Distinctive: line 135
Do not inventory files, functions, or proposed implementation steps that are not required to define the problem or completion criteria.
- Distinctive: line 154
If the user explicitly asked to file an issue, skip the preview — file it and share the link.
- Very specific: line 160
Write the body to a uniquely named temp file, then pass it with --body-file.
- Very specific: line 161
Do not inline the body with shell substitution (--body "$(cat <<'EOF' ...)") — multiline text can be corrupted by pasted output or escaping …
- Very specific: line 180
Add kind-appropriate labels (bug, experiment).
- Distinctive: line 184
Before creating the issue, re-open the body file and verify it contains no unrelated shell output (pre-commit logs, pytest session headers, …
- Very specific: line 188
After creating the issue, fetch its published text with gh issue view "$issue_url" --json title,body and correct any text added or altered …
- Distinctive: line 203
Never credit yourself in the issue.
- Very specific: line 204
Always add the agent-generated label.
- Distinctive: line 207
If the conversation does not contain a clear bug or actionable improvement, say so and ask the user what they want to file.
- Distinctive: line 209
Use the smallest matching body structure.
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Vendored from marin-community/marin-style v0.3.0 — do not edit; re-run `marin-style sync`. -->Skill: File GitHub Issue
Create a GitHub issue in the current repository from bugs, regressions, or
improvements identified in the current conversation. gh defaults to the repo of
the current checkout; pass --repo <owner>/<name> only to target a different one.
Background
Read first: AGENTS.md.
Before drafting, read:
.agents/skills/writing-style/SKILL.md.agents/skills/writing-style/issues.md.agents/skills/writing-style/ai-writing-donts.md
Issue Kinds and Body Structure
Pick the kind, then use the matching body structure below. There are no GitHub issue templates — these structures live here.
| Kind | When to use | Labels |
| bug | A bug or regression was found | bug, agent-generated |
| task | An improvement, refactor, or feature request | agent-generated + priority if known |
| experiment | An experiment needs tracking | experiment, agent-generated |
Bug body
<what is broken and its impact -- concrete symptoms or error messages>
Reproduce:
1. <step>
2. <step>
Expected: <what should happen instead>
<optional: concise evidence or confirmed root cause>Task body
<what needs to be done and why -- enough context for anyone on the team>
Done when:
<specific, testable completion criteria>Experiment body
## TL;DR
<One-paragraph current summary. Leave blank only when the work is just being kicked off.>
## Description
<Context someone outside the thread can understand.>
## Hypothesis or Goal
<What are you trying to learn, fix, or achieve?>
## Status
<Current state; update as evidence lands.>
## Links
* Logbook:
* Report:
* Important updates:
## Decision Log
## ConclusionWorkflow
1. Gather Context from Conversation
Extract from the conversation:
- What is broken or missing -- concrete symptoms, error messages, failing test output.
- Where it happens -- file paths, line numbers, module names.
- How to reproduce -- steps, commands, or minimal config that triggers it.
- Root cause (if known).
- Severity -- blocks work, causes data loss, or cosmetic?
If it's ambiguous what to file, ask the user before proceeding.
2. Classify the Issue
Pick the kind (bug, task, or experiment). If unsure, ask the user.
3. Duplicate Check
Search for existing issues first:
gh issue list --state open --search "<keyword>"If a match exists, tell the user and offer to comment on it instead.
4. Draft the Issue
Title: At most 80 characters, optionally prefixed with a scope tag. State a
factual symptom for a bug (e.g. [training] Gradient accumulation drops the last
microbatch) and an imperative outcome for a task (e.g. [training] Handle
partial accumulation steps). Do not add bug:, task:, or another type
prefix.
Body: Use the section structure for the chosen kind (see above).
Rules for the body:
- No filler ("I noticed...", "During our conversation...").
- No markdown images or tables.
- Reference code with
file:linelinks, not inline dumps. - Keep every fact needed to understand and act on the issue. Remove history, repetition, and implementation narration that does not define the problem or completion criteria; experiment issues may retain more tracking context.
- Do not repeat the title in a
Descriptionsection. - Do not inventory files, functions, or proposed implementation steps that are not required to define the problem or completion criteria.
- Include error messages or stack traces in code blocks, trimmed to the relevant frames.
- For task issues: include concrete
Done whencriteria. - For bug issues: include numbered reproduction steps.
5. Compress and Inspect the Payload
Apply the writing-style final compression pass to the exact title and body that will be sent to GitHub. For a bug or task, verify the title is at most 80 characters. Every remaining sentence must add a symptom, impact, reproduction step, observation, expected behavior, or completion criterion.
This review is required even when the user explicitly asked to file the issue. It is an author self-check, not a request for approval.
6. Confirm or File Directly
If the user explicitly asked to file an issue, skip the preview — file it and share the link. If the agent surfaced the issue (not explicitly requested), show the drafted title and body and wait for approval or edits.
7. File the Issue
Write the body to a uniquely named temp file, then pass it with --body-file.
Do not inline the body with shell substitution (--body "$(cat <<'EOF' ...)")
— multiline text can be corrupted by pasted output or escaping mistakes. Do not
reuse a fixed path like /tmp/issue-body.md; concurrent agent runs can
overwrite each other's drafts on shared hosts.
body_file="$(mktemp "${TMPDIR:-/tmp}/issue-body.XXXXXX.md")"
trap 'rm -f "$body_file"' EXIT
cat > "$body_file" <<'EOF'
<body>
EOF
issue_url="$(gh issue create \
--title "<title>" \
--label "agent-generated" \
--body-file "$body_file")"Add kind-appropriate labels (bug, experiment). If a relevant label does not
exist, skip it rather than creating new labels. For task issues, add a priority
label (p1, p2, p3) if the user specifies one or severity is clear.
Before creating the issue, re-open the body file and verify it contains no unrelated shell output (pre-commit logs, pytest session headers, prompt transcripts). If it does, clean the draft before posting.
After creating the issue, fetch its published text with
gh issue view "$issue_url" --json title,body and correct any text added or
altered by the publishing tool.
8. Report Back
Print the issue URL.
Writing Style
Terse: every sentence conveys new information; no preamble or editorializing; no restating code a link covers; annotate code links, don't narrate them.
Rules
- Never credit yourself in the issue.
- Always add the
agent-generatedlabel. - Confirm with the user before filing only when the agent surfaced the issue (not when the user explicitly asked to file).
- If the conversation does not contain a clear bug or actionable improvement, say so and ask the user what they want to file.
- Use the smallest matching body structure. Omit optional context and headings that add no information.
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.

