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 Investigation

by kernitus in kernitus/BukkitOldCombatMechanics

A skill your agent uses for GitHub issue triage and local investigation, including gh issue workflows, picking a fresh issue, reproducing issue reports, and planning regression coverage.

MPL-2.0Auto-check passedDevelopment

Install GitHub Issue Investigation

skills CLI
$ npx skills add kernitus/BukkitOldCombatMechanics --skill github-issue-investigation -a claude-code

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

GitHub CLI
$ gh skill install kernitus/BukkitOldCombatMechanics github-issue-investigation --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/kernitus/BukkitOldCombatMechanics.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/github-issue-investigation .claude/skills/github-issue-investigation && 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
github-issue-investigation
GitHub stars
225
Token cost
~953 tokens
SKILL.md length
489 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MPL-2.0

At a glance

A skill your agent uses for GitHub issue triage and local investigation, including gh issue workflows, picking a fresh issue, reproducing issue reports, and planning regression coverage.

  • GitHub issue triage and local investigation
  • SKILL.md covers Default posture, When an issue number or URL is…, When no issue is provided and Reproduction and coverage, plus 1 more section
  • Calls gh
  • Including gh issue workflows

What it does

GitHub Issue Investigation is an agent skill from kernitus/BukkitOldCombatMechanics. Use for GitHub issue triage and local investigation, including gh issue workflows, picking a fresh issue, reproducing issue reports, and planning regression coverage.

Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Issue triage. It works with GitHub. The repository describes itself as: Minecraft plugin to configure combat mechanics for 1.9 onwards. The licence is MPL-2.0.

When your agent uses it

  • GitHub issue triage and local investigation
  • Including gh issue workflows
  • Picking a fresh issue
  • Reproducing issue reports

Example prompts

  • “/github-issue-investigation”

What it can do on your machine

Read from SKILL.md and the folder at commit e66e7a9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    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

GitHub Issue Investigation loads about 953 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 489 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 kernitus/BukkitOldCombatMechanics at commit e66e7a9, republished under its MPL-2.0 licence (© kernitus). 489 words, ~953 tokens.

Download SKILL.mdSave it as .claude/skills/github-issue-investigation/SKILL.md (or your agent's skills folder).
name
github-issue-investigation
description
Use for GitHub issue triage and local investigation, including gh issue workflows, picking a fresh issue, reproducing issue reports, and planning regression coverage.

GitHub Issue Investigation

Use this skill when investigating GitHub issues locally, especially bug reports that may need reproduction and durable regression coverage before any fix is attempted.

Default posture

  • Treat GitHub as read-only by default.
  • gh issue list and gh issue view are allowed for investigation.
  • Do not comment, label, assign, close, edit milestones, or otherwise mutate public GitHub state unless the user explicitly asks later.
  • Keep findings chat-only by default; do not create plans, state files, or persistent notes unless the user asks.
  • Try to reproduce before fixing. Prefer a regression test that can remain in the repository when practical.
  • After local findings, let the user decide whether to fix, comment, or abandon the issue.

When an issue number or URL is provided

Inspect that specific issue with gh issue view. Summarise:

  • reported behaviour and expected behaviour;
  • environment, configuration, server, plugin, or version hints;
  • missing information that would affect local reproduction;
  • related code paths and existing tests worth checking;
  • a local reproduction recommendation, including the narrowest likely test or manual scenario.

Avoid changing GitHub state while doing this. If the issue is clearly a duplicate, support question, feature request, or waiting for reporter information, report that and explain whether local investigation is still worthwhile.

When no issue is provided

Use gh issue list to build a shortlist rather than choosing silently. Present about 3-5 candidate issues with:

  • issue number and title;
  • why the issue looks actionable;
  • likely affected area;
  • reproduction feasibility;
  • reasons to avoid it, if any.

Do not require or prefer positive labels. Actively avoid issues labelled exactly awaiting testing or effectively equivalent, because those are usually awaiting reporter or user verification rather than fresh local investigation.

Prefer issues with observable broken behaviour and enough detail to reproduce. Avoid issues that are obvious duplicates, support questions, feature requests, waiting on reporter information, already assigned or visibly in progress, dependent on unavailable external services, private servers, client-only behaviour, or anything requiring GitHub-side mutation before local investigation can proceed.

Show full SKILL.md (160 more words)Show less

Reproduction and coverage

  • Reproduce before implementing a fix where practical.
  • Prefer integration tests when the behaviour depends on Bukkit/Paper server behaviour, plugin lifecycle, events, fake players, PacketEvents, or cross-version compatibility.
  • Use or trigger integration-test-verification for integration-test matrix selection, runs, Kotest registration, compact result triage, and failure investigation.
  • Respect the repository rule that root and user-facing agents must not read full build/integration-test-logs/*.log files directly; use compact summaries first and delegate log inspection only when needed.
  • If integration coverage is not feasible, explain why and propose the next best durable coverage, such as a focused unit-level test, synthetic event test, or documented manual reproduction.

Routing after investigation

Keep this skill investigation-focused. If the user later requests a fix:

  • use TDD for repro-test-first work;
  • use Planner when the fix needs planned multi-step work or broader design decisions;
  • use BuildReview for small standalone quick changes.

Do not start a fix, comment on GitHub, or create persistent planning artefacts merely because an issue looks actionable.

© kernitus, MPL-2.0. 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 .agents/skills/github-issue-investigation of kernitus/BukkitOldCombatMechanics.

Open the folder on GitHubat commit e66e7a9

Compare with similar skills

GitHub Issue Investigation 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 Investigation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Issue Investigation this skillkernitus/BukkitOldCombatMechanics225—~953Automated safety check: PassMPL-2.0
Setup Matt Pocock Skillsbestofjs/bestofjs3.1k20 repos~1.7kAutomated 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
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
WinAppSDK Triage Meeting Prepmicrosoft/WindowsAppSDK4.7k—~2.8kAutomated safety check: PassApache-2.0

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

  • 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 yesterday
    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 yesterday
    DevelopmentAuto-check passed

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • WinAppSDK Triage Meeting Prep

    microsoft/WindowsAppSDK

    Official

    Prepares the triage meeting summary for WinAppSDK Needs-Triage issues, with research-backed area suggestions, draft replies and a diff since the last triage.

    4.7k GitHub stars~2.8k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • A2ui Issue Triage

    a2ui-project/a2ui

    Automates the triage of GitHub issues in the A2UI repository.

    17k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

More from kernitus/BukkitOldCombatMechanics

All 9 skills in this repo

  • Integration Test Verification

    kernitus/BukkitOldCombatMechanics

    A skill your agent uses when running, selecting, authoring, or triaging integration tests, Kotest specs, Gradle matrix tasks, FakePlayer-backed test cases, or compact test-result files; do not use…

    225 GitHub stars~1.2k tokensUpdated 4 days ago
    Auto-check passed

  • Dependabot PR Review

    kernitus/BukkitOldCombatMechanics

    A skill your agent uses for Dependabot PRs, dependency bumps, Gradle or Maven dependency updates, GitHub Actions updates, dependency changelog/licence/release-note review, JVM/classfile checks, and…

    225 GitHub stars~882 tokensUpdated 4 days ago
    Auto-check passed

  • Module Config Change

    kernitus/BukkitOldCombatMechanics

    A skill your agent uses for config.yml, module enablement, modesets, config migration, configurable module assignment, and per-module option changes; do not use for unrelated integration-test…

    225 GitHub stars~914 tokensUpdated 4 days ago
    Auto-check passed

  • PR Draft Summary

    kernitus/BukkitOldCombatMechanics

    A skill your agent uses when drafting pull-request titles, descriptions, change summaries, risk notes, validation sections, or reviewer handoff text; do not use for implementation design, release…

    225 GitHub stars~526 tokensUpdated 4 days ago
    Auto-check passed

  • Release Readiness Review

    kernitus/BukkitOldCombatMechanics

    A skill your agent uses for GitHub release, Hangar, CurseForge/BukkitDev upload, Spigot release handoff, licence, asset naming, supported-version, and workflow readiness checks; do not use for…

    225 GitHub stars~1.5k tokensUpdated 4 days ago
    Auto-check passed

  • User Facing Changelog

    kernitus/BukkitOldCombatMechanics

    A skill your agent uses when rewriting CHANGELOG.md, GitHub release notes, or Release Please PR changelog sections into user-facing release notes; do not use for release publishing, assets, licence…

    225 GitHub stars~1.3k tokensUpdated 4 days ago
    Auto-check passed

Works with

Categories

Questions about GitHub Issue Investigation

What does GitHub Issue Investigation do?

A skill your agent uses for GitHub issue triage and local investigation, including gh issue workflows, picking a fresh issue, reproducing issue reports, and planning regression coverage. GitHub Issue Investigation is an agent skill from kernitus/BukkitOldCombatMechanics. Use for GitHub issue triage and local investigation, including gh issue workflows, picking a fresh issue, reproducing issue reports, and planning regression coverage.

When should I use GitHub Issue Investigation?

GitHub Issue Investigation fits situations like: GitHub issue triage and local investigation; including gh issue workflows; picking a fresh issue; reproducing issue reports.

How do I install GitHub Issue Investigation in Claude Code?

Run `npx skills add kernitus/BukkitOldCombatMechanics --skill github-issue-investigation -a claude-code`. Or copy the skill folder (.agents/skills/github-issue-investigation in kernitus/BukkitOldCombatMechanics) into .claude/skills/github-issue-investigation in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Issue Investigation in Codex?

Run `npx skills add kernitus/BukkitOldCombatMechanics --skill github-issue-investigation -a codex`. Or copy the skill folder (.agents/skills/github-issue-investigation in kernitus/BukkitOldCombatMechanics) into .agents/skills/github-issue-investigation in your project. Codex loads it when a task matches its description.

Can I use GitHub Issue Investigation 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 kernitus/BukkitOldCombatMechanics --skill github-issue-investigation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-issue-investigation, .gemini/skills/github-issue-investigation, .github/skills/github-issue-investigation and .opencode/skills/github-issue-investigation in your project.

What does GitHub Issue Investigation need to run?

Going by SKILL.md and its folder, GitHub Issue Investigation needs the command-line tools its instructions call (gh).

Does GitHub Issue Investigation 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 GitHub Issue Investigation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitHub Issue Investigation use?

GitHub Issue Investigation is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Issue Investigation use?

About 953 tokens (SKILL.md is roughly 3.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 Investigation?

Skills that share tags, products or a category with GitHub Issue Investigation: Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars), Windows App SDK Issue Triage Report (microsoft/WindowsAppSDK, 4.7k stars), Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars) and Pre-Release PR Triage (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Issue Investigation?

kernitus (a GitHub user) maintains it in kernitus/BukkitOldCombatMechanics, which has 225 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 4, 2026.

Source: kernitus/BukkitOldCombatMechanics on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.