Index of every page on this site: llms.txt
All skills
Run it yourself

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

Use this Skill: https://skilld.dev/gh/homeassistant-ai/ha-mcp/issue-analysis

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈88 tokens for metadata: the name and description. ≈637 when used: this file.

Description uses 4.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈351 characters, or 4.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill is designed to automate the analysis and management of GitHub issues for a specific repository. It uses standard GitHub CLI tools and incorporates a human-in-the-loop confirmation step before applying any changes.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: MEDIUM · 1 issue

Signed by skilld at 955af7b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 6 months ago
What it can do
Runs commands Reads files Network
Modelopus
argument-hint
<issue-number>
model
opus
All 6 allowed tools
BashReadGlobGrepWebFetchWebSearch

README badge

README badge for homeassistant-ai/ha-mcp/issue-analysis