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.
Create a GitHub issue using the wingman issue templates (bug, feature).
Install Issue
$ npx skills add dedalus-labs/wingman --skill issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dedalus-labs/wingman 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/dedalus-labs/wingman.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/issue .claude/skills/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 "issue" agent skill from https://github.com/dedalus-labs/wingman/tree/main/.agents/skills/issue into .claude/skills/issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/dedalus-labs/wingman/tree/main/.agents/skills/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 dedalus-labs/wingman --skill issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dedalus-labs/wingman issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dedalus-labs/wingman.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/issue .agents/skills/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 "issue" agent skill from https://github.com/dedalus-labs/wingman/tree/main/.agents/skills/issue into .agents/skills/issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 dedalus-labs/wingman --skill issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dedalus-labs/wingman issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dedalus-labs/wingman.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/issue .cursor/skills/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 "issue" agent skill from https://github.com/dedalus-labs/wingman/tree/main/.agents/skills/issue into .cursor/skills/issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/dedalus-labs/wingman.git --path .agents/skills/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 dedalus-labs/wingman --skill issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dedalus-labs/wingman issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dedalus-labs/wingman.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/issue .gemini/skills/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 "issue" agent skill from https://github.com/dedalus-labs/wingman/tree/main/.agents/skills/issue into .gemini/skills/issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 dedalus-labs/wingman 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 dedalus-labs/wingman --skill issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dedalus-labs/wingman.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/issue .github/skills/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 "issue" agent skill from https://github.com/dedalus-labs/wingman/tree/main/.agents/skills/issue into .github/skills/issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 dedalus-labs/wingman --skill 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 dedalus-labs/wingman issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dedalus-labs/wingman.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/issue .opencode/skills/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 "issue" agent skill from https://github.com/dedalus-labs/wingman/tree/main/.agents/skills/issue into .opencode/skills/issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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
issue- GitHub stars
- 181
- Token cost
- ~517 tokens
- SKILL.md length
- 225 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create a GitHub issue using the wingman issue templates (bug, feature).
- Works in 6 steps: Parse $ARGUMENTS → Read the matching template file from… → Fill every section. Leave no placeholder… → …
- Development work in your project
- SKILL.md covers Context (auto-detected from…, Template Selection, Rules and Task
- Calls git and gh
What it does
Issue is an agent skill from dedalus-labs/wingman. Create a GitHub issue using the wingman issue templates (bug, feature). Injects branch and commit context automatically.
Its SKILL.md is about 520 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with GitHub. The repository describes itself as: scaling capability quotient. The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/issue”
Requirements
- Pre-approved tools (allowed-tools): Bash(git *), Bash(gh *), Read
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Parse $ARGUMENTS
- Read the matching template file from .github/ISSUE_TEMPLATE/.
- Fill every section. Leave no placeholder text. If a section truly has no content, write
- Auto-inject the branch and last-commit context into "Additional Context".
- Run gh issue create with the right labels.
- Return the issue URL.
What it can do on your machine
Read from SKILL.md and the folder at commit f6233ab. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(git *)Bash(gh *)Read
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and 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
Issue loads about 517 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 225 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 dedalus-labs/wingman at commit f6233ab, republished under its MIT licence (© dedalus-labs). 225 words, ~517 tokens.
Download SKILL.mdSave it as
.claude/skills/issue/SKILL.md (or your agent's skills folder).- name
- issue
- description
- Create a GitHub issue using the wingman issue templates (bug, feature). Injects branch and commit context automatically.
- allowed-tools
- Bash(git *), Bash(gh *), Read
- argument-hint
- <bug|feature> <title>
Context (auto-detected from HEAD)
- Current branch: !
git branch --show-current - Last commit: !
git log -1 --oneline - Remote: !
git remote get-url origin
Template Selection
Parse the first positional arg from $ARGUMENTS as the issue type:
| Type | Template file | Labels |
|---|---|---|
| bug | .github/ISSUE_TEMPLATE/bug_report.yml | bug,triage |
| feature | .github/ISSUE_TEMPLATE/feature_request.yml | enhancement |
The bug_report.yml file is a GitHub issue form. gh issue create --body submits plain
markdown, so translate the yaml form fields into a markdown body with the same section
headings (Bug Description, Steps to Reproduce, Expected Behavior, Environment,
Additional Context).
For feature_request.yml, read the file and translate form fields the same way.
Rules
- Issue title: short, imperative, no period, under 80 chars. No conventional-commit prefix (that's for PRs, not issues).
- The remaining positional args from
$ARGUMENTS(after the type) form the title. - Use
gh issue create --title "..." --body "$(cat <<'EOF' ... EOF)" --label "...". - Labels come from the table above. Do not invent new labels.
Task
- Parse
$ARGUMENTS:- First token: issue type (
bugorfeature). If missing or invalid, ask the user which template to use. - Remaining tokens: title.
- First token: issue type (
- Read the matching template file from
.github/ISSUE_TEMPLATE/. - Fill every section. Leave no placeholder text. If a section truly has no content, write "N/A" rather than deleting the section.
- Auto-inject the branch and last-commit context into "Additional Context".
- Run
gh issue createwith the right labels. - Return the issue URL.
© dedalus-labs, MIT. 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/issue of dedalus-labs/wingman.
Open the folder on GitHubat commit f6233ab
Compare with similar skills
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 |
|---|---|---|---|---|---|---|
| Issue this skilldedalus-labs/wingman | 181 | — | ~517 | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Setup Matt Pocock Skillsbestofjs/bestofjs | 3.1k | 20 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT |
Similar skills
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.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
Setup Matt Pocock Skills
bestofjs/bestofjs
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
More from dedalus-labs/wingman
Greentext
dedalus-labs/wingman
Explain system behavior, request flows, architecture, or implementation logic as short 4chan-style greentext lines.
Better Interface
dedalus-labs/wingman
Design engineering principles for making TUI interfaces feel polished.
PR Review
dedalus-labs/wingman
Review PR comments from GitHub. An agent skill from dedalus-labs/wingman.
Promote
dedalus-labs/wingman
Create a changelog-style promotion PR between two branches. An agent skill from dedalus-labs/wingman.
PR
dedalus-labs/wingman
Create a pull request using the wingman PR template. An agent skill from dedalus-labs/wingman.
Commit
dedalus-labs/wingman
Create a git commit with conventional commit format. An agent skill from dedalus-labs/wingman.
Related
Works with
Categories
Questions about Issue
What does Issue do?
Create a GitHub issue using the wingman issue templates (bug, feature). Issue is an agent skill from dedalus-labs/wingman. Create a GitHub issue using the wingman issue templates (bug, feature).
When should I use Issue?
Issue fits situations like: development work in your project.
How do I install Issue in Claude Code?
Run `npx skills add dedalus-labs/wingman --skill issue -a claude-code`. Or copy the skill folder (.agents/skills/issue in dedalus-labs/wingman) into .claude/skills/issue in your project. Claude Code loads it when a task matches its description.
How do I install Issue in Codex?
Run `npx skills add dedalus-labs/wingman --skill issue -a codex`. Or copy the skill folder (.agents/skills/issue in dedalus-labs/wingman) into .agents/skills/issue in your project. Codex loads it when a task matches its description.
Can I use 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 dedalus-labs/wingman --skill 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/issue, .gemini/skills/issue, .github/skills/issue and .opencode/skills/issue in your project.
What does Issue need to run?
Going by SKILL.md and its folder, Issue needs the command-line tools its instructions call (git and gh). Its frontmatter pre-approves these tools: Bash(git *), Bash(gh *), Read.
Does Issue access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is 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 Issue use?
Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Issue use?
About 517 tokens (SKILL.md is roughly 2.1k 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 Issue?
Skills that share tags, products or a category with Issue: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Issue?
dedalus-labs (a GitHub organization) maintains it in dedalus-labs/wingman, which has 181 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on April 25, 2026.
Source: dedalus-labs/wingman on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.