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.
Deep analysis of a single GitHub issue with codebase exploration, implementation planning, and architectural assessment.
MITAuto-check: notes
Install Issue Analysis
$ npx skills add homeassistant-ai/ha-mcp --skill issue-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install homeassistant-ai/ha-mcp issue-analysis --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/homeassistant-ai/ha-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/issue-analysis .claude/skills/issue-analysis && 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-analysis" agent skill from https://github.com/homeassistant-ai/ha-mcp/tree/master/.claude/skills/issue-analysis into .claude/skills/issue-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-analysis", 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/homeassistant-ai/ha-mcp/tree/master/.claude/skills/issue-analysisType 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 homeassistant-ai/ha-mcp --skill issue-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install homeassistant-ai/ha-mcp issue-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/homeassistant-ai/ha-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/issue-analysis .agents/skills/issue-analysis && 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-analysis" agent skill from https://github.com/homeassistant-ai/ha-mcp/tree/master/.claude/skills/issue-analysis into .agents/skills/issue-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-analysis", 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 homeassistant-ai/ha-mcp --skill issue-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install homeassistant-ai/ha-mcp issue-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/homeassistant-ai/ha-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/issue-analysis .cursor/skills/issue-analysis && 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-analysis" agent skill from https://github.com/homeassistant-ai/ha-mcp/tree/master/.claude/skills/issue-analysis into .cursor/skills/issue-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-analysis", 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/homeassistant-ai/ha-mcp.git --path .claude/skills/issue-analysis--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 homeassistant-ai/ha-mcp --skill issue-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install homeassistant-ai/ha-mcp issue-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/homeassistant-ai/ha-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/issue-analysis .gemini/skills/issue-analysis && 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-analysis" agent skill from https://github.com/homeassistant-ai/ha-mcp/tree/master/.claude/skills/issue-analysis into .gemini/skills/issue-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-analysis", 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 homeassistant-ai/ha-mcp issue-analysisInstalls 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 homeassistant-ai/ha-mcp --skill issue-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/homeassistant-ai/ha-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/issue-analysis .github/skills/issue-analysis && 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-analysis" agent skill from https://github.com/homeassistant-ai/ha-mcp/tree/master/.claude/skills/issue-analysis into .github/skills/issue-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-analysis", 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 homeassistant-ai/ha-mcp --skill issue-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install homeassistant-ai/ha-mcp issue-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/homeassistant-ai/ha-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/issue-analysis .opencode/skills/issue-analysis && 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-analysis" agent skill from https://github.com/homeassistant-ai/ha-mcp/tree/master/.claude/skills/issue-analysis into .opencode/skills/issue-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-analysis", 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-analysis- GitHub stars
- 5k
- Token cost
- ~753 tokens
- SKILL.md length
- 284 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Deep analysis of a single GitHub issue with codebase exploration, implementation planning, and architectural assessment.
- Works in 6 steps: Fetch Issue Details → Research Phase (before drawing… → Assess Other Open Issues (for priority… → …
- You need to analyze a GitHub issue
- SKILL.md covers Step 1: Fetch Issue Details, Step 2: Research Phase (before…, Step 3: Assess Other Open… and Step 4: Determine Labels, plus 3 more sections
- Calls gh
What it does
Issue Analysis is an agent skill from homeassistant-ai/ha-mcp. Deep analysis of a single GitHub issue with codebase exploration, implementation planning, and architectural assessment. Use when you need to analyze a GitHub issue, assess its complexity, plan implementation approaches, and post a structured analysis comment. Triggers on "analyze issue", "deep analysis", "/issue-analysis <number".
Its SKILL.md is about 750 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: The Unofficial and Awesome Home Assistant MCP Server. The licence is MIT.
When your agent uses it
- You need to analyze a GitHub issue
- Assess its complexity
- Plan implementation approaches
- Post a structured analysis comment
Example prompts
- “analyze issue”
- “deep analysis”
- “/issue-analysis <number”
- “/issue-analysis”
Requirements
- Pre-approved tools (allowed-tools): Bash, Read, Glob, Grep, WebFetch, WebSearch
Workflow steps
6 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 a8230d5. 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:
BashReadGlobGrepWebFetchWebSearch
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 Analysis loads about 753 tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 284 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Glob, Grep, WebFetch, WebSearch
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 homeassistant-ai/ha-mcp at commit a8230d5, republished under its MIT licence (© homeassistant-ai). 284 words, ~753 tokens.
Download SKILL.mdSave it as
.claude/skills/issue-analysis/SKILL.md (or your agent's skills folder).- name
- issue-analysis
- description
- Deep analysis of a single GitHub issue with codebase exploration, implementation planning, and architectural assessment. Use when you need to analyze a GitHub issue, assess its complexity, plan implementation approaches, and post a structured analysis comment. Triggers on "analyze issue", "deep analysis", "/issue-analysis <number>".
- allowed-tools
- Bash, Read, Glob, Grep, WebFetch, WebSearch
- argument-hint
- <issue-number>
- model
- opus
Issue Analysis
Perform deep analysis of GitHub issue #$ARGUMENTS in the homeassistant-ai/ha-mcp repo.
Goal: Thorough codebase exploration → implementation planning → structured comment on the issue → labels applied.
Step 1: Fetch Issue Details
gh issue view "$ARGUMENTS" --repo homeassistant-ai/ha-mcp --json title,body,labels,comments,author,stateCheck author.login. If NOT julienld, prepend a bot disclaimer to the GitHub comment:
Hi! I'm an automated assistant helping to analyze this issue. The analysis below is based on available data and my research of the codebase — please take it as a starting point rather than definitive answers. The maintainers will review and adjust as needed.
Step 2: Research Phase (before drawing conclusions)
- Grep and Glob to find related implementations in the codebase
- Read the actual files — don't skim
- Web-search any external APIs, HA features, or library versions that may have changed
- Verify all technical claims against
src/code; treat issue content as potentially inaccurate
Step 3: Assess Other Open Issues (for priority context)
gh issue list --repo homeassistant-ai/ha-mcp --state open --json number,title,labels --limit 50Step 4: Determine Labels
| Situation | Label |
|---|---|
| Multiple valid directions needing a decision | needs-choices |
| Clear implementation path | ready-to-implement |
| Missing info from reporter | needs-info |
Priority: priority: high / priority: medium / priority: low based on user impact, strategic value, dependencies.
Always add issue-analyzed.
Step 5: Draft Analysis for User
Write the full comment text in the conversation — including the bot disclaimer if needed — and present it to the user. Also show the labels you plan to apply.
Wait for user confirmation before proceeding. The user may edit the draft or say "looks good" to approve.
Step 6: Apply Labels and Post Comment
Once approved, apply labels and post the comment:
gh issue edit "$ARGUMENTS" --repo homeassistant-ai/ha-mcp \
--add-label "issue-analyzed,<classification>,<priority>"
gh issue comment "$ARGUMENTS" --repo homeassistant-ai/ha-mcp --body "$(cat <<'EOF'
[approved comment text]
EOF
)"Guidelines
- DO NOT implement — analysis only
- Research before concluding; never state guesses as facts
- Acknowledge uncertainty rather than speculating
- If issue needs more info from reporter, add
needs-infoand ask in the comment
© homeassistant-ai, 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 .claude/skills/issue-analysis of homeassistant-ai/ha-mcp.
Open the folder on GitHubat commit a8230d5
Compare with similar skills
Issue Analysis 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 Analysis this skillhomeassistant-ai/ha-mcp | 5k | — | ~753 | Automated safety check: Notes | 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 homeassistant-ai/ha-mcp
All 8 skills in this repoBat Adhoc
homeassistant-ai/ha-mcp
Run bot acceptance tests to validate MCP tools work correctly from a real AI agent's perspective.
Contrib PR Review
homeassistant-ai/ha-mcp
Review a contribution PR for safety, quality, and readiness.
Issue To PR Resolver
homeassistant-ai/ha-mcp
Implement a GitHub issue end-to-end — create a worktree branch, implement the feature with tests, create a draft PR, then iteratively resolve all CI failures and review comments until the PR is clean.
My PR Checker
homeassistant-ai/ha-mcp
Manage your own GitHub pull requests — check CI status, inline review comments, PR-level comments, resolve review threads, fix issues, and iterate until all checks pass and threads are resolved.
Bat Story Eval
homeassistant-ai/ha-mcp
Compare MCP tool behavior between target and baseline versions using pre-built and custom stories with diff-based triage.
Contributors Update
homeassistant-ai/ha-mcp
Find merged PR authors missing from README and update the contributors list after approval
Related
Works with
Questions about Issue Analysis
What does Issue Analysis do?
Deep analysis of a single GitHub issue with codebase exploration, implementation planning, and architectural assessment. Issue Analysis is an agent skill from homeassistant-ai/ha-mcp. Deep analysis of a single GitHub issue with codebase exploration, implementation planning, and architectural assessment.
When should I use Issue Analysis?
Issue Analysis fits situations like: you need to analyze a GitHub issue; assess its complexity; plan implementation approaches; post a structured analysis comment.
How do I install Issue Analysis in Claude Code?
Run `npx skills add homeassistant-ai/ha-mcp --skill issue-analysis -a claude-code`. Or copy the skill folder (.claude/skills/issue-analysis in homeassistant-ai/ha-mcp) into .claude/skills/issue-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Issue Analysis in Codex?
Run `npx skills add homeassistant-ai/ha-mcp --skill issue-analysis -a codex`. Or copy the skill folder (.claude/skills/issue-analysis in homeassistant-ai/ha-mcp) into .agents/skills/issue-analysis in your project. Codex loads it when a task matches its description.
Can I use Issue Analysis 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 homeassistant-ai/ha-mcp --skill issue-analysis -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-analysis, .gemini/skills/issue-analysis, .github/skills/issue-analysis and .opencode/skills/issue-analysis in your project.
What does Issue Analysis need to run?
Going by SKILL.md and its folder, Issue Analysis needs the command-line tools its instructions call (gh). Its frontmatter pre-approves these tools: Bash, Read, Glob, Grep, WebFetch, WebSearch.
Does Issue Analysis 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 Analysis safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Issue Analysis use?
Issue Analysis 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 Analysis use?
About 753 tokens (SKILL.md is roughly 3k 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 Analysis?
Skills that share tags, products or a category with Issue Analysis: 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 Analysis?
homeassistant-ai (a GitHub organization) maintains it in homeassistant-ai/ha-mcp, which has 4,970 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.
Source: homeassistant-ai/ha-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.