PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
File a GitHub issue only when explicitly requested or delegated by another selected workflow; do not create issues merely because a problem was found.
Apache-2.0Auto-check passed
Install File Issue
$ npx skills add marin-community/marin --skill file-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install marin-community/marin file-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/marin-community/marin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/file-issue .claude/skills/file-issue && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "file-issue" agent skill from https://github.com/marin-community/marin/tree/main/.agents/skills/file-issue into .claude/skills/file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/marin-community/marin/tree/main/.agents/skills/file-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add marin-community/marin --skill file-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install marin-community/marin file-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marin-community/marin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/file-issue .agents/skills/file-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "file-issue" agent skill from https://github.com/marin-community/marin/tree/main/.agents/skills/file-issue into .agents/skills/file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add marin-community/marin --skill file-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install marin-community/marin file-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marin-community/marin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/file-issue .cursor/skills/file-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "file-issue" agent skill from https://github.com/marin-community/marin/tree/main/.agents/skills/file-issue into .cursor/skills/file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/marin-community/marin.git --path .agents/skills/file-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add marin-community/marin --skill file-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install marin-community/marin file-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marin-community/marin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/file-issue .gemini/skills/file-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "file-issue" agent skill from https://github.com/marin-community/marin/tree/main/.agents/skills/file-issue into .gemini/skills/file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install marin-community/marin file-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add marin-community/marin --skill file-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/marin-community/marin.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/file-issue .github/skills/file-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "file-issue" agent skill from https://github.com/marin-community/marin/tree/main/.agents/skills/file-issue into .github/skills/file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add marin-community/marin --skill file-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install marin-community/marin file-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marin-community/marin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/file-issue .opencode/skills/file-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "file-issue" agent skill from https://github.com/marin-community/marin/tree/main/.agents/skills/file-issue into .opencode/skills/file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
file-issue- GitHub stars
- 3.9k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 455 words
- Files
- 1
- Skills in repo
- 41
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
File a GitHub issue only when explicitly requested or delegated by another selected workflow; do not create issues merely because a problem was found.
- Works in 7 steps: Gather and classify → Check duplicates → Draft → …
- SKILL.md covers Issue Kinds and Body Structure and Workflow
- Calls gh
What it does
File Issue is an agent skill from marin-community/marin. File a GitHub issue only when explicitly requested or delegated by another selected workflow; do not create issues merely because a problem was found.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with GitHub. The repository describes itself as: Open-source framework for the research and development of foundation models. The licence is Apache-2.0.
Example prompts
- “/file-issue”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit be1f5f1. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
File Issue loads about 1.1k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 455 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from marin-community/marin at commit be1f5f1, republished under its Apache-2.0 licence (© marin-community). 455 words, ~1,126 tokens.
Download SKILL.mdSave it as
.claude/skills/file-issue/SKILL.md (or your agent's skills folder).- name
- file-issue
- description
- File a GitHub issue only when explicitly requested or delegated by another selected workflow; do not create issues merely because a problem was found.
File a GitHub issue
Before drafting, read AGENTS.md and:
.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 smallest matching structure.
| 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:
* W&B Report:
* Important updates:
## Decision Log
## ConclusionWorkflow
1. Gather and classify
Extract the symptom or desired outcome, impact, location, reproduction, known cause, and severity. Ask when the issue or its kind is ambiguous.
2. Check duplicates
Search for existing issues first:
gh issue list --repo marin-community/marin --state open --search "<keyword>"If a match exists, tell the user and offer to comment on it instead.
3. Draft
Title: At most 80 characters, optionally prefixed with a scope tag. State a
factual symptom for a bug (e.g. [levanter] Gradient accumulation drops the last microbatch) and an imperative outcome for a task (e.g. [levanter] Handle partial accumulation steps). Do not add bug:, task:, or another type
prefix.
Use the body structure above. Keep the facts needed to act; link code with
file:line, trim errors to relevant frames, and omit filler, repeated titles,
diff inventories, and unnecessary implementation narration. Bugs need numbered
reproduction steps; tasks need testable completion criteria.
4. 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.
Show full SKILL.md (204 more words)Show less
5. Apply the approval boundary
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.
6. 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 --repo marin-community/marin \
--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.
7. Report
Print the issue URL.
© marin-community, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/file-issue of marin-community/marin.
Open the folder on GitHubat commit be1f5f1
Compare with similar skills
File Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| File Issue this skillmarin-community/marin | 3.9k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Superpowers Sessionsobra/superpowers | 296k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 83k | 5 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Update V8 Versionopeninterpreter/openinterpreter | 69k | 2 repos | ~845 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Update V8 Version
openinterpreter/openinterpreter
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
More from marin-community/marin
All 41 skills in this repoNoslop
marin-community/marin
Deslop, simplify, or review low-value tests and prose only when explicitly requested for a branch or diff.
Use Iris
marin-community/marin
Use Iris to submit, inspect, debug, monitor, or recover jobs and tasks; diagnose scheduling and federation; deploy controllers; or reserve dev GPUs and TPUs.
Launch Rl
marin-community/marin
Define, validate, submit, or restart a Marin SkyRL experiment through its artifact main.
Marina Applet
marin-community/marin
Build, validate, publish, update, inspect, query, roll back, or archive a dynamic Marina applet.
Query Finelog
marin-community/marin
Query Finelog logs and telemetry for Iris tasks, workers, profiles, training, vLLM, and cross-cluster forwarding.
Trace Pulumi Diff
marin-community/marin
Run a read-only preview for a specified Marin infra/pulumi stack and trace each pending resource change to merged pull requests since its latest successful update when that update records a clean…
Related
Works with
Questions about File Issue
What does File Issue do?
File a GitHub issue only when explicitly requested or delegated by another selected workflow; do not create issues merely because a problem was found. File Issue is an agent skill from marin-community/marin. File a GitHub issue only when explicitly requested or delegated by another selected workflow; do not create issues merely because a problem was found.
How do I install File Issue in Claude Code?
Run `npx skills add marin-community/marin --skill file-issue -a claude-code`. Or copy the skill folder (.agents/skills/file-issue in marin-community/marin) into .claude/skills/file-issue in your project. Claude Code loads it when a task matches its description.
How do I install File Issue in Codex?
Run `npx skills add marin-community/marin --skill file-issue -a codex`. Or copy the skill folder (.agents/skills/file-issue in marin-community/marin) into .agents/skills/file-issue in your project. Codex loads it when a task matches its description.
Can I use File Issue in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add marin-community/marin --skill file-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/file-issue, .gemini/skills/file-issue, .github/skills/file-issue and .opencode/skills/file-issue in your project.
What does File Issue need to run?
Going by SKILL.md and its folder, File Issue needs the command-line tools its instructions call (gh).
Does File Issue access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is File Issue safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does File Issue use?
File Issue is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does File Issue use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to File Issue?
Skills that share tags, products or a category with File Issue: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains File Issue?
marin-community (a GitHub organization) maintains it in marin-community/marin, which has 3,902 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 8, 2026.
Source: marin-community/marin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.