SkillsAdd

homeassistant-ai/ha-mcp · Archived

issue-analysis

Deep analysis of a single GitHub issue with codebase exploration, implementation planning, and architectural assessment.

First seen Aug 23, 2026

Installation

$ npx skills add homeassistant-ai/ha-mcp --skill issue-analysis
View on skills.sh ↗ GitHub repository ↗

Summary

  • 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>".

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

issue-to-pr-resolver Same source
homeassistant-ai/ha-mcp

Implement a GitHub issue end-to-end — create a worktree branch, implement the feature with test…

1 installs
wt Same source
homeassistant-ai/ha-mcp

Create a git worktree in worktree/ subdirectory with up-to-date master

1 installs
my-pr-checker Same source
homeassistant-ai/ha-mcp

Manage your own GitHub pull requests — check CI status, inline review comments, PR-level commen…

1 installs
contributors-update Same source
homeassistant-ai/ha-mcp

Find merged PR authors missing from README and update the contributors list after approval

1 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from homeassistant-ai/ha-mcp.

npx skills add homeassistant-ai/ha-mcp
issue-to-pr-resolver 1 wt 1 my-pr-checker 1 contributors-update 1 contrib-pr-review 1 bat-story-eval 1 bat-adhoc 1

Browse all from homeassistant-ai/ha-mcp

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 4.5K
License LICENSE
Default branch master
Open issues 8
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsBash, Read, Glob, Grep, WebFetch, WebSearch

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,027 B
  • docs SUMMARY.md 356 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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,state

Check 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 50

Step 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-info and ask in the comment