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.
GitHub issue creation skill. An agent skill from team-attention/hoyeon.
MITAuto-check passed
Install Issue
$ npx skills add team-attention/hoyeon --skill issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install team-attention/hoyeon 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/team-attention/hoyeon.git skills-src && mkdir -p .claude/skills && cp -r skills-src/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/team-attention/hoyeon/tree/main/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/team-attention/hoyeon/tree/main/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 team-attention/hoyeon --skill issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install team-attention/hoyeon issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .agents/skills && cp -r skills-src/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/team-attention/hoyeon/tree/main/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 team-attention/hoyeon --skill issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install team-attention/hoyeon issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/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/team-attention/hoyeon/tree/main/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/team-attention/hoyeon.git --path 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 team-attention/hoyeon --skill issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install team-attention/hoyeon issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/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/team-attention/hoyeon/tree/main/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 team-attention/hoyeon 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 team-attention/hoyeon --skill issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .github/skills && cp -r skills-src/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/team-attention/hoyeon/tree/main/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 team-attention/hoyeon --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 team-attention/hoyeon issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/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/team-attention/hoyeon/tree/main/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
- 173
- Token cost
- ~1.4k tokens
- SKILL.md length
- 507 words
- Files
- 1
- Skills in repo
- 36
- Repo updated
- First seen
- Licence
- MIT
At a glance
GitHub issue creation skill. An agent skill from team-attention/hoyeon.
- Works in 3 steps: Impact Analysis → Preview & Confirm → Create Issue
- SKILL.md covers Input, Phase 1: Impact Analysis, Phase 2: Preview & Confirm and Phase 3: Create Issue, plus 2 more sections
- Calls gh
What it does
Issue is an agent skill from team-attention/hoyeon. GitHub issue creation skill. Analyzes the entire codebase impact based on user request, then creates a structured issue with AI-verified/human-judgment-needed/caution sections. /issue "issue description" Trigger: "/issue", "이슈 만들어", "issue 만들자", "깃헙 이슈"
Its SKILL.md is about 1.4k 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: Requirements-first Harness — derive, verify, execute. The licence is MIT.
Example prompts
- “issue description”
- “/issue”
- “issue 만들자”
- “/issue”
Workflow steps
3 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 7cff032. 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
Issue loads about 1.4k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 507 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 team-attention/hoyeon at commit 7cff032, republished under its MIT licence (© team-attention). 507 words, ~1,382 tokens.
Download SKILL.mdSave it as
.claude/skills/issue/SKILL.md (or your agent's skills folder).- name
- issue
- description
- GitHub issue creation skill. Analyzes the entire codebase impact based on user request, then creates a structured issue with AI-verified/human-judgment-needed/caution sections. /issue "issue description" Trigger: "/issue", "이슈 만들어", "issue 만들자", "깃헙 이슈"
- validate_prompt
- Must complete with one of: 1. GitHub issue created (URL returned) 2. User cancelled after preview Must NOT: create issue without user confirmation, skip…
/issue — Structured GitHub Issue Creator
Investigate the codebase based on the user's request and create a GitHub issue with clearly defined confidence boundaries.
Input
The text the user typed after /issue is the original request. Preserve it verbatim.
Examples:
/issue Duplicate Shorts URL fetches in YouTube subscription feed/issue Add notification settings tab to Settings page/issue Scheduler occasionally runs twice
If the input is too vague (e.g., "there's a bug"), ask ONE clarifying question. Otherwise, start investigating immediately.
Phase 1: Impact Analysis
Perform a full impact analysis based on the user's request. Use Agent to investigate in parallel.
What to Investigate
Launch agents in parallel where possible:
- Related code exploration — Identify files, functions, and modules directly related to the request
- Dependency analysis — Where is this code referenced, and which modules are affected
- Existing test coverage — Whether related tests exist and what they cover
- Related issues/history — Relevant change history from git log, known issues
Classifying Findings
Classify all findings into three confidence levels:
✅ AI Verified
Objective facts confirmed through code exploration. No need for human re-verification.
- Function/file locations, call relationships
- Whether tests exist
- Current behavior (as read directly from code)
- Relevant config values, environment variables
🤔 Decision Required
Decision points that AI cannot make on your behalf.
- Trade-off choices (performance vs. accuracy, UX vs. security, etc.)
- Business logic decisions
- Scope decisions (how much to fix)
- Priority judgment
⚠️ Human Verify
Risks and caveats AI may have missed.
- Potential side effects
- Risks from production environment differences
- External service dependencies
- Whether data migration is needed
- Areas AI could not verify (external systems, real user data, etc.)
Phase 2: Preview & Confirm
After investigation, show the user a preview of the issue body.
Issue Body Template
## Request
> {original text the user typed after /issue, verbatim}
## Impact Analysis
### Related Code
- `file:line` — description
- ...
### Scope of Impact
- List of affected modules/features
---
## ✅ AI Verified
> Facts confirmed through code exploration. No further verification needed.
- [ ] Confirmed fact 1
- [ ] Confirmed fact 2
## 🤔 Decision Required
> Decision points requiring human judgment.
- [ ] Decision point 1 — Option A vs B, considerations
- [ ] Decision point 2
## ⚠️ Human Verify
> Risks AI may have missed. Needs human review before and/or after implementation.
- [ ] Verification point 1 — why this needs checking
- [ ] Verification point 2After showing the preview, confirm with AskUserQuestion:
AskUserQuestion(
question: "Should I create a GitHub issue with this content?",
header: "Issue Preview",
options: [
{ label: "Create", description: "Create the issue as-is" },
{ label: "Edit then create", description: "I want to make changes first" },
{ label: "Cancel", description: "Do not create the issue" }
]
)- Create → Proceed to Phase 3
- Edit then create → Incorporate user feedback, then show preview again
- Cancel → "Issue creation cancelled." → Stop
Show full SKILL.md (196 more words)Show less
Phase 3: Create Issue
Create the issue with gh issue create.
gh issue create --title "Issue title" --body "$(cat <<'EOF'
Issue body
EOF
)"Title Rules
- Under 70 characters
- Use a prefix:
feat:,fix:,refactor:,chore:, etc. (based on content) - English or Korean OK
Label Auto-mapping
Based on the issue content, add matching labels via the --label flag using the table below.
Multiple labels allowed. If no match, create without labels.
| Issue type | Label |
|---|---|
| Bug, error, broken behavior | bug |
| New feature, addition, improvement | enhancement |
| Documentation related | documentation |
| Question, investigation, needs clarification | question |
After creation, return the issue URL to the user.
Hard Rules
- Investigate first — Never create an issue without investigation
- Confirm first — Never create an issue without user confirmation
- Preserve original — The user's original request must be included verbatim in the "Request" section
- Facts only — AI Verified contains only things directly confirmed from code. No speculation.
- Be honest — Anything unverified goes into Human Verify. Never pretend to know.
- Keep it concise — Do not let the issue body grow unnecessarily long
Checklist Before Stopping
- Codebase impact analysis completed
- Findings classified into three confidence levels
- User's original request included verbatim
- User reviewed the preview
-
gh issue createexecuted and URL returned (or user cancelled)
© team-attention, 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 skills/issue of team-attention/hoyeon.
Open the folder on GitHubat commit 7cff032
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 skillteam-attention/hoyeon | 173 | — | ~1.4k | Automated safety check: Pass | MIT | |
| 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 team-attention/hoyeon
All 36 skills in this repoSkill Session Analyzer
team-attention/hoyeon
This skill should be used when the user asks to "analyze session", "evaluate skill execution", "check session logs", provides a session ID with a skill path, or wants to verify that a skill executed…
Browser Work
team-attention/hoyeon
Recon-first browser automation. An agent skill from team-attention/hoyeon.
Check
team-attention/hoyeon
This skill should be used when the user wants to verify their changes before pushing, or update the project's rule checklists.
Compound
team-attention/hoyeon
This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR.
QA
team-attention/hoyeon
Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen.
Dev Scan
team-attention/hoyeon
Collect diverse opinions on technical topics from developer communities.
Related
Works with
Questions about Issue
What does Issue do?
GitHub issue creation skill. An agent skill from team-attention/hoyeon. Issue is an agent skill from team-attention/hoyeon. GitHub issue creation skill.
How do I install Issue in Claude Code?
Run `npx skills add team-attention/hoyeon --skill issue -a claude-code`. Or copy the skill folder (skills/issue in team-attention/hoyeon) 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 team-attention/hoyeon --skill issue -a codex`. Or copy the skill folder (skills/issue in team-attention/hoyeon) 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 team-attention/hoyeon --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 (gh).
Does 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 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 1.4k tokens (SKILL.md is roughly 5.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 Issue?
Skills that share tags, products or a category with 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 Issue?
team-attention (a GitHub organization) maintains it in team-attention/hoyeon, which has 173 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on May 21, 2026.
Source: team-attention/hoyeon on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.