New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

GitHub Issue Analysis

by gittower in gittower/git-flow-next

Analyzes a GitHub issue for the git-flow-next project and writes an analysis document under .ai/ that covers the affected code and proposes TODO comments.

Custom licenceAuto-check: notesDevelopment

Install GitHub Issue Analysis

skills CLI
$ npx skills add gittower/git-flow-next --skill analyze-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install gittower/git-flow-next analyze-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/gittower/git-flow-next.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/analyze-issue .claude/skills/analyze-issue && rm -rf skills-src

Use ~/.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/

Facts

Skill name
analyze-issue
GitHub stars
458
Used in
1 other repo
Token cost
~694 tokens
SKILL.md length
142 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
Custom licence

At a glance

Analyzes a GitHub issue for the git-flow-next project and writes an analysis document under .ai/ that covers the affected code and proposes TODO comments.

  • Works in 5 steps: Fetch Issue Details → Create Workflow Directory → Explore the Codebase → …
  • Starting work on a git-flow-next issue and wanting a written analysis first
  • SKILL.md covers Instructions and Analysis Template
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Given an issue number, the agent fetches the title, description, labels and linked issues from the gittower/git-flow-next repository through the GitHub issue tool. It creates a folder under `.ai/` named for the issue number and a slug of up to four title words, such as `.ai/issue-42-squash-merge/`, and then explores the codebase for related code, affected components, the current implementation and similar patterns or prior art.

The findings go into an `analysis.md` file built from a template in the SKILL.md. Where specific code locations need attention, the agent suggests TODO comments that reference the issue number. It closes by reporting the path of the analysis file, summarizing the key findings and suggesting the next step, which is to create a feature branch and run `/create-plan`.

When your agent uses it

  • Starting work on a git-flow-next issue and wanting a written analysis first
  • Mapping which components an issue would touch before planning a change
  • Leaving TODO markers at the code locations an issue affects

Example prompts

  • “Analyze issue 42 in git-flow-next and write the analysis to .ai/.”
  • “Look at the squash merge request issue and tell me which parts of the code it affects.”
  • “Before planning the fix, write up what the issue needs and where the code lives.”

Requirements

  • A checkout of git-flow-next
  • Access to GitHub issues through the GitHub tool
  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Write, Bash, mcp__github__get_issue

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Fetch Issue Details
  2. Create Workflow Directory
  3. Explore the Codebase
  4. Write Analysis Document
  5. Propose TODO Comments

What it can do on your machine

Read from SKILL.md and the folder at commit 00d1b4b. 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:

    • Read
    • Grep
    • Glob
    • Write
    • Bash
    • mcp__github__get_issue

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

GitHub Issue Analysis loads about 694 tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 142 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~18
When it runs · the whole SKILL.md, loaded when a task matches
~694

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: Read, Grep, Glob, Write, Bash, mcp__github__get_issue

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 142 words (~694 tokens).

“Perform detailed analysis of a GitHub issue and write the analysis to the .ai directory.”

— opening of SKILL.md by gittower, Custom licence
name
analyze-issue
allowed-tools
Read, Grep, Glob, Write, Bash, mcp__github__get_issue
argument-hint
<issue-number>

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/analyze-issue of gittower/git-flow-next.

Open the folder on GitHubat commit 00d1b4b

Used in 1 other repository

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gittower/git-flow-next, which our catalogue first saw on October 7, 2026.

Compare with similar skills

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

GitHub Issue Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Issue Analysis this skillgittower/git-flow-next4581 repos~694Automated safety check: NotesCustom licence
Setup Matt Pocock Skillsbestofjs/bestofjs3.1k20 repos~1.7kAutomated safety check: PassMIT
Update .NET OS Packagesdotnet/core22k—~2.3kAutomated safety check: PassMIT
Windows App SDK Issue Triage Reportmicrosoft/WindowsAppSDK4.7k—~3.4kAutomated safety check: PassApache-2.0
Exposed Bug Fix WorkflowJetBrains/Exposed9.3k—~3.8kAutomated safety check: PassApache-2.0
Beautify GitHub Readmeoil-oil/beautify-github-readme1.8k—~4.1kAutomated safety check: PassMIT

Similar skills

  • Setup Matt Pocock Skills

    bestofjs/bestofjs

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.

    3.1k GitHub starsUsed in 20 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Update .NET OS Packages

    dotnet/core

    Official

    Audits and updates os-packages.json files listing the Linux packages each .NET release needs per distro, then regenerates the Markdown from the JSON.

    22k GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Windows App SDK Issue Triage Report

    microsoft/WindowsAppSDK

    Official

    Generates GitHub Feature Area Status reports for the Windows App SDK repository, scoring issues so teams can see what needs attention in each area.

    4.7k GitHub stars~3.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Exposed Bug Fix Workflow

    JetBrains/Exposed

    Official

    Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.

    9.3k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Beautify GitHub Readme

    oil-oil/beautify-github-readme

    Redesign GitHub README homepages or create project-native pure SVG, hybrid SVG-composed PNG/WebP, and opt-in animated GIF assets.

    1.8k GitHub stars~4.1k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Library Documentation Seeker

    withkynam/vibecode-pro-max-kit

    Looks up library and framework documentation through Context7 first, with bundled Node scripts as a fallback that fetch and analyze llms.txt files.

    1.1k GitHub starsUsed in 2 repos~1k tokens
    DevelopmentAuto-check: notes

More from gittower/git-flow-next

All 25 skills in this repo

  • PR Review Feedback Handler

    gittower/git-flow-next

    Fetches review comments on a pull request, judges each one, writes the evaluation to a plan file and implements accepted changes, waiting for approval before anything public.

    458 GitHub stars~2.9k tokensUpdated 1 mo ago
    Auto-check: notes

  • Stale PR Review Check

    gittower/git-flow-next

    Scans open pull requests against the project's review response window and reports which ones need action, read-only unless you approve a reminder.

    458 GitHub stars~549 tokensUpdated 1 mo ago
    Auto-check: notes

  • Local Code Review

    gittower/git-flow-next

    Reviews local commits, branch diffs or pull requests against project guidelines and writes the result to local files, never posting it to GitHub.

    458 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check: notes

  • Commit with Project Guidelines

    gittower/git-flow-next

    Creates a commit that follows the project's COMMIT_GUIDELINES.md, choosing the type by what the change does and verifying the result.

    458 GitHub stars~818 tokensUpdated 1 mo ago
    Auto-check: notes

  • Test-First Implementation Plan

    gittower/git-flow-next

    Builds a two-phase implementation plan from a spec issue, analysis or concept, writing a detailed test plan first and the implementation outline second.

    458 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check: notes

  • Create Spec

    gittower/git-flow-next

    Create a Codex-gated spec issue from a triaged report, concept, or idea

    458 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check: notes

Works with

Categories

Questions about GitHub Issue Analysis

What does GitHub Issue Analysis do?

Analyzes a GitHub issue for the git-flow-next project and writes an analysis document under .ai/ that covers the affected code and proposes TODO comments. Given an issue number, the agent fetches the title, description, labels and linked issues from the gittower/git-flow-next repository through the GitHub issue tool.ai/issue-42-squash-merge/`, and then explores the codebase for related code, affected components, the current implementation and similar patterns or prior art.

When should I use GitHub Issue Analysis?

GitHub Issue Analysis fits situations like: starting work on a git-flow-next issue and wanting a written analysis first; mapping which components an issue would touch before planning a change; leaving TODO markers at the code locations an issue affects.

How do I install GitHub Issue Analysis in Claude Code?

Run `npx skills add gittower/git-flow-next --skill analyze-issue -a claude-code`. Or copy the skill folder (.claude/skills/analyze-issue in gittower/git-flow-next) into .claude/skills/analyze-issue in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Issue Analysis in Codex?

Run `npx skills add gittower/git-flow-next --skill analyze-issue -a codex`. Or copy the skill folder (.claude/skills/analyze-issue in gittower/git-flow-next) into .agents/skills/analyze-issue in your project. Codex loads it when a task matches its description.

Can I use GitHub 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 gittower/git-flow-next --skill analyze-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/analyze-issue, .gemini/skills/analyze-issue, .github/skills/analyze-issue and .opencode/skills/analyze-issue in your project.

What does GitHub Issue Analysis need to run?

SKILL.md names no scripts, command-line tools or credentials: GitHub Issue Analysis is instructions for the agent only. Our summary lists: A checkout of git-flow-next; Access to GitHub issues through the GitHub tool. Its frontmatter pre-approves these tools: Read, Grep, Glob, Write, Bash, mcp__github__get_issue.

Does GitHub Issue Analysis access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is GitHub 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 GitHub Issue Analysis use?

GitHub Issue Analysis has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does GitHub Issue Analysis use?

About 694 tokens (SKILL.md is roughly 2.8k 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 GitHub Issue Analysis?

Skills that share tags, products or a category with GitHub Issue Analysis: Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars), Update .NET OS Packages (dotnet/core, 22k stars), Windows App SDK Issue Triage Report (microsoft/WindowsAppSDK, 4.7k stars) and Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Issue Analysis?

gittower (a GitHub organization) maintains it in gittower/git-flow-next, which has 458 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on September 8, 2026.

Source: gittower/git-flow-next on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.