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.
Analyze a problem description against the current repository, draft a repository-aware GitHub issue in English, and create it using the GH tool.
No licenceAuto-check passed
Install GitHub Issue Writer
$ npx skills add Th4nat0s/Chall_Tools --skill github-issue-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Th4nat0s/Chall_Tools github-issue-writer --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/Th4nat0s/Chall_Tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/issue-writer .claude/skills/github-issue-writer && 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 "github-issue-writer" agent skill from https://github.com/Th4nat0s/Chall_Tools/tree/master/skills/issue-writer into .claude/skills/github-issue-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-writer", 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/Th4nat0s/Chall_Tools/tree/master/skills/issue-writerType 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 Th4nat0s/Chall_Tools --skill github-issue-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Th4nat0s/Chall_Tools github-issue-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Th4nat0s/Chall_Tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/issue-writer .agents/skills/github-issue-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "github-issue-writer" agent skill from https://github.com/Th4nat0s/Chall_Tools/tree/master/skills/issue-writer into .agents/skills/github-issue-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-writer", 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 Th4nat0s/Chall_Tools --skill github-issue-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Th4nat0s/Chall_Tools github-issue-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Th4nat0s/Chall_Tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/issue-writer .cursor/skills/github-issue-writer && 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 "github-issue-writer" agent skill from https://github.com/Th4nat0s/Chall_Tools/tree/master/skills/issue-writer into .cursor/skills/github-issue-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-writer", 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/Th4nat0s/Chall_Tools.git --path skills/issue-writer--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 Th4nat0s/Chall_Tools --skill github-issue-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Th4nat0s/Chall_Tools github-issue-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Th4nat0s/Chall_Tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/issue-writer .gemini/skills/github-issue-writer && 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 "github-issue-writer" agent skill from https://github.com/Th4nat0s/Chall_Tools/tree/master/skills/issue-writer into .gemini/skills/github-issue-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-writer", 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 Th4nat0s/Chall_Tools github-issue-writerInstalls 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 Th4nat0s/Chall_Tools --skill github-issue-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Th4nat0s/Chall_Tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/issue-writer .github/skills/github-issue-writer && 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 "github-issue-writer" agent skill from https://github.com/Th4nat0s/Chall_Tools/tree/master/skills/issue-writer into .github/skills/github-issue-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-writer", 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 Th4nat0s/Chall_Tools --skill github-issue-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Th4nat0s/Chall_Tools github-issue-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Th4nat0s/Chall_Tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/issue-writer .opencode/skills/github-issue-writer && 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 "github-issue-writer" agent skill from https://github.com/Th4nat0s/Chall_Tools/tree/master/skills/issue-writer into .opencode/skills/github-issue-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-writer", 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
github-issue-writer- GitHub stars
- 108
- Token cost
- ~1.7k tokens
- SKILL.md length
- 574 words
- Files
- 2
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- None found
At a glance
Analyze a problem description against the current repository, draft a repository-aware GitHub issue in English, and create it using the GH tool.
- Works in 9 steps: Parse the command alias and complete… → Identify the repository with GH. Stop if… → Search related issues and PRs with… → …
- The user enters ghissue
- SKILL.md covers Commands, Language, Required Tooling and Workflow, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
GitHub Issue Writer is an agent skill from Th4nat0s/Chall_Tools. Analyze a problem description against the current repository, draft a repository-aware GitHub issue in English, and create it using the GH tool. Use when the user enters ghissue or ghadd followed by a problem description; quotation marks are optional when the remaining input is one description.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It works with GitHub. The repository describes itself as: Tools for security challenges.
When your agent uses it
- The user enters ghissue
- Ghadd followed by a problem description
- Quotation marks are optional when the remaining input is one description
Example prompts
- “/github-issue-writer”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Parse the command alias and complete problem description. Extract explicit constraints, expected behavior, affected components, and…
- Identify the repository with GH. Stop if owner, repo, or default branch cannot be confirmed.
- Search related issues and PRs with important terms from the description, relevant file names, symbols, error messages, and config…
- Do not create a duplicate when an equivalent active issue exists. If likely duplicate equivalence is uncertain, report it instead of…
- Inspect current repository implementation through GH. Confirm current behavior, abstractions, conventions, validation, error handling…
- Classify required change: new code, modified code, removal, refactor, config, deployment, infrastructure, DB/schema, API, docs, tests…
- Analyze relevant risks only: compatibility, security, authn/authz, data integrity, resource use, concurrency, performance, failure…
- Draft concise English title and structured Markdown body using the required template.
- Create the issue with GH only when repository identification, repo inspection, duplicate checks, and authorization all succeed.
What it can do on your machine
Read from SKILL.md and the folder at commit 259e5ce. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
GitHub Issue Writer loads about 1.7k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 574 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 574 words (~1,738 tokens).
- name
- github-issue-writer
Files
SKILL.md and 1 other file in skills/issue-writer of Th4nat0s/Chall_Tools.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 259e5ce
Compare with similar skills
GitHub Issue Writer 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 |
|---|---|---|---|---|---|---|
| GitHub Issue Writer this skillTh4nat0s/Chall_Tools | 108 | — | ~1.7k | Automated safety check: Pass | None | |
| 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 Th4nat0s/Chall_Tools
Caveman
Th4nat0s/Chall_Tools
Ultra-compressed communication mode. An agent skill from Th4nat0s/Chall_Tools.
Ghfix
Th4nat0s/Chall_Tools
Git Hub issue fix skill. An agent skill from Th4nat0s/Chall_Tools.
Edithdoc
Th4nat0s/Chall_Tools
A skill your agent uses when the task involves creating, reading, editing, updating, fixing, or undoing notes on the CSIRT HedgeDoc/HDOC instance through the edithdoc MCP server, including any hdoc.
Related
Works with
Questions about GitHub Issue Writer
What does GitHub Issue Writer do?
Analyze a problem description against the current repository, draft a repository-aware GitHub issue in English, and create it using the GH tool. GitHub Issue Writer is an agent skill from Th4nat0s/Chall_Tools. Analyze a problem description against the current repository, draft a repository-aware GitHub issue in English, and create it using the GH tool.
When should I use GitHub Issue Writer?
GitHub Issue Writer fits situations like: the user enters ghissue; ghadd followed by a problem description; quotation marks are optional when the remaining input is one description.
How do I install GitHub Issue Writer in Claude Code?
Run `npx skills add Th4nat0s/Chall_Tools --skill github-issue-writer -a claude-code`. Or copy the skill folder (skills/issue-writer in Th4nat0s/Chall_Tools) into .claude/skills/github-issue-writer in your project. Claude Code loads it when a task matches its description.
How do I install GitHub Issue Writer in Codex?
Run `npx skills add Th4nat0s/Chall_Tools --skill github-issue-writer -a codex`. Or copy the skill folder (skills/issue-writer in Th4nat0s/Chall_Tools) into .agents/skills/github-issue-writer in your project. Codex loads it when a task matches its description.
Can I use GitHub Issue Writer 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 Th4nat0s/Chall_Tools --skill github-issue-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-issue-writer, .gemini/skills/github-issue-writer, .github/skills/github-issue-writer and .opencode/skills/github-issue-writer in your project.
What does GitHub Issue Writer need to run?
SKILL.md names no scripts, command-line tools or credentials: GitHub Issue Writer is instructions for the agent only.
Does GitHub Issue Writer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is GitHub Issue Writer 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 GitHub Issue Writer use?
No licence was found for GitHub Issue Writer or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does GitHub Issue Writer use?
About 1.7k tokens (SKILL.md is roughly 7k 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 GitHub Issue Writer?
Skills that share tags, products or a category with GitHub Issue Writer: 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 GitHub Issue Writer?
Th4nat0s (a GitHub user) maintains it in Th4nat0s/Chall_Tools, which has 108 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 16, 2026.
Source: Th4nat0s/Chall_Tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.