Issue Analysis

OrganizationPopular

homeassistant-ai

issue-analysis

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

Overview

Publisher	homeassistant-ai
Repository	`ha-mcp`
Skill name	`issue-analysis`
Stars	5K
Forks	233
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by homeassistant-ai on GitHub. Read the source before you install it.

Installation

Install the Issue Analysis AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/homeassistant-ai/ha-mcp/tree/master/.claude/skills/issue-analysis
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/homeassistant-ai/ha-mcp.git /tmp/ha-mcp
mkdir -p .claude/skills
cp -r /tmp/ha-mcp/.claude/skills/issue-analysis .claude/skills/issue-analysis

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Issue Analysis in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Issue Analysis on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Issue Analysis is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

bash
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)

bash
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:

bash
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

Frequently asked questions

What does the Issue Analysis AI skill do?

Why use Issue Analysis on TypingMind?

Because you install it once and use it with any model. Issue Analysis is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Issue Analysis in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/homeassistant-ai/ha-mcp/tree/master/.claude/skills/issue-analysis. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Issue Analysis?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Issue Analysis?

As many as you like. As long as a model supports skills, you can use Issue Analysis with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Issue Analysis AI skill free?

Yes. It is published on GitHub by homeassistant-ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Solid

openclaw

OrganizationPopular

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Auto Qa

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Autoreview

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Issue Analysis

Step 1: Fetch Issue Details

Step 2: Research Phase (before drawing conclusions)

Step 3: Assess Other Open Issues (for priority context)

Step 4: Determine Labels

Step 5: Draft Analysis for User

Step 6: Apply Labels and Post Comment

Guidelines

Frequently asked questions

Related AI Skills

Set up your own AI workspace now