Issue Triage
pnp/powershell
Take a PnP PowerShell GitHub issue, find the cmdlet that owns it, trace the code path, and decide whether the cause is in this repo or in PnP Framework, PnP Core SDK or the service.
Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.
Install Triage Issues
$ npx skills add ClickHouse/clickhouse-java --skill triage-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ClickHouse/clickhouse-java triage-issues --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ClickHouse/clickhouse-java.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/triage-issues .claude/skills/triage-issues && rm -rf skills-srcUse ~/.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/
Install the "triage-issues" agent skill from https://github.com/ClickHouse/clickhouse-java/tree/main/.cursor/skills/triage-issues into .claude/skills/triage-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issues", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ClickHouse/clickhouse-java/tree/main/.cursor/skills/triage-issuesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ClickHouse/clickhouse-java --skill triage-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ClickHouse/clickhouse-java triage-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ClickHouse/clickhouse-java.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/triage-issues .agents/skills/triage-issues && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "triage-issues" agent skill from https://github.com/ClickHouse/clickhouse-java/tree/main/.cursor/skills/triage-issues into .agents/skills/triage-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issues", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ClickHouse/clickhouse-java --skill triage-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ClickHouse/clickhouse-java triage-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ClickHouse/clickhouse-java.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/triage-issues .cursor/skills/triage-issues && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "triage-issues" agent skill from https://github.com/ClickHouse/clickhouse-java/tree/main/.cursor/skills/triage-issues into .cursor/skills/triage-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issues", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ClickHouse/clickhouse-java.git --path .cursor/skills/triage-issues--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ClickHouse/clickhouse-java --skill triage-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ClickHouse/clickhouse-java triage-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ClickHouse/clickhouse-java.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/triage-issues .gemini/skills/triage-issues && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "triage-issues" agent skill from https://github.com/ClickHouse/clickhouse-java/tree/main/.cursor/skills/triage-issues into .gemini/skills/triage-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issues", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ClickHouse/clickhouse-java triage-issuesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ClickHouse/clickhouse-java --skill triage-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ClickHouse/clickhouse-java.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/triage-issues .github/skills/triage-issues && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "triage-issues" agent skill from https://github.com/ClickHouse/clickhouse-java/tree/main/.cursor/skills/triage-issues into .github/skills/triage-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issues", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ClickHouse/clickhouse-java --skill triage-issues -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ClickHouse/clickhouse-java triage-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ClickHouse/clickhouse-java.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/triage-issues .opencode/skills/triage-issues && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "triage-issues" agent skill from https://github.com/ClickHouse/clickhouse-java/tree/main/.cursor/skills/triage-issues into .opencode/skills/triage-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issues", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
triage-issues- GitHub stars
- 1.6k
- Token cost
- ~904 tokens
- SKILL.md length
- 420 words
- Files
- 3
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.
- Works in 3 steps: Preview → Research → Summary
- The user asks to triage an issue
- SKILL.md covers Stage 1: Preview, Stage 2: Research and Stage 3: Summary
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Triage Issues is an agent skill from ClickHouse/clickhouse-java. Analyzes a single GitHub issue at a time. Reads the description, defines labels and priority, researches additional information, and provides a short but detailed report. Use when the user asks to triage an issue, analyze a bug report, or categorize a GitHub issue.
Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `references.md` and `source-map.md`).
It sits in Testing & QA, covering Issue triage and QA and bug reports. It works with GitHub and ClickHouse. The repository describes itself as: ClickHouse Java Clients & JDBC Driver. The licence is Apache-2.0.
When your agent uses it
- The user asks to triage an issue
- Analyze a bug report
- Categorize a GitHub issue
Example prompts
- “Use the triage-issues skill to analyz a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java”
- “/triage-issues”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 67a6b9e. 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
No scripts in the folder and no shell commands in SKILL.md.
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
Triage Issues loads about 904 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 420 words of instructions outside code blocks.
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 ClickHouse/clickhouse-java at commit 67a6b9e, republished under its Apache-2.0 licence (© ClickHouse). 420 words, ~904 tokens.
Download SKILL.mdSave it as
.claude/skills/triage-issues/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- triage-issues
- description
- Analyzes a single GitHub issue at a time. Reads the description, defines labels and priority, researches additional information, and provides a short but detailed report. Use when the user asks to triage an issue, analyze a bug report, or categorize a GitHub issue.
- disable-model-invocation
- true
Issue Triage Workflow
Stage 1: Preview
- Sizes the description into categories: Tiny, Small, Medium, Large. See Description Sizes in references.md for size definitions.
- Analyzes based on description size:
- Tiny: Tries to detect what module is affected. Uses specific terms and method names. JDBC, for example, has very recognizable sets of methods. Remembers or outputs additional information.
- Small or Medium: Finds what module or functionality is affected and records this information. Small or Medium descriptions just need more technical details.
- Large: Refines and compacts the issue for further investigation. Large descriptions should have enough data to pinpoint the problem but are often in a form hardly readable by humans, so creates a minimal version.
- Checks that there is minimal data available about the problem. See Minimal Issue Details in references.md.
Stage 2: Research
Before exploring the tree, use source-map.md to locate the
affected module and area:* labels (module/package boundaries, label → source
location, entry-point classes, and stacktrace → module heuristics). Only grep
the source once the map has narrowed the scope.
Every issue type has its own research approach.
Question
- Looks up documentation first if there is related information. See Module Documentation in references.md.
- If the question is about how configuration works - explores source code. See Module Sources in references.md.
- If the question is about usage then generates a set of questions to get details about the use-case.
- Else, notes that this question needs human attention.
Show full SKILL.md (180 more words)Show less
Potential Bug
- Finds out scope: determines the module, what configuration parameters are involved, and what classes implement the area.
- If there is a stacktrace, adds the call chain of methods for review.
- If there is a specific code example given, looks at what functions are called in what order.
- Understands the runtime environment more. Generates questions to discover more.
- If JDBC, then there could be some framework involved. Finds out what the conditions should be.
- If client, then the application environment is important.
- When the user provides a data example or use case description, creates a test scenario or code. Keeps code minimal.
What to ask User
- Asks user about specific version of client or JDBC driver. Asks about specific version of server.
- Asks about network setup if relevant. For example, issue related network may be affected by proxy in the middle.
- Asks about reproducibility of the problem if it is network related and looks like have unstable nature.
Stage 3: Summary
When finishing the analysis, outputs the findings using this exact template:
## Triage Report
**Effort to Fix**: [Tiny/Small/Medium/Large]
**Type**: [Question/Bug]
**Affected Module**: [Module Name]
### Summary
[1-2 sentences summarizing the core issue]
### Recommended Labels & Priority
- Labels: [label1, label2]
### Missing Information / Questions for User
1. [Question 1]
2. [Question 2]
### Tests to Add
**Test 1: Scenario**
```
// code
```
**Test 2: Scenario**
```
// code
```© ClickHouse, Apache-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
SKILL.md and 2 other files in .cursor/skills/triage-issues of ClickHouse/clickhouse-java.
- SKILL.md
- references.md
- source-map.md
Open the folder on GitHubat commit 67a6b9e
Compare with similar skills
Triage Issues 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Triage Issues this skillClickHouse/clickhouse-java | 1.6k | — | ~904 | Automated safety check: Pass | Apache-2.0 | |
| Issue Triagepnp/powershell | 905 | — | ~1.8k | Automated safety check: Pass | MIT | |
| GitHub Issue Creatoraiskillstore/marketplace | 430 | 3 repos | ~1k | Automated safety check: Pass | None | |
| Bug Report TriageOrchestratorInc/agent-orchestrator | 13k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| OpenROAD Issue TriageThe-OpenROAD-Project/OpenROAD | 3.2k | — | ~842 | Automated safety check: Pass | BSD-3-Clause | |
| Triage Issuesoftspark/ai-toolkit | 179 | — | ~1.3k | Automated safety check: Notes | Apache-2.0 |
Similar skills
GitHub Issue Creator
aiskillstore/marketplace
Turn error logs, screenshots, voice notes, and rough bug reports into crisp, developer-ready GitHub issues with repro steps, impact, and evidence.
Bug Report Triage
OrchestratorInc/agent-orchestrator
Helps a reporter describe a bug, searches for duplicates and gathers diagnostic evidence kept separate from a short, human-worded issue draft.
OpenROAD Issue Triage
The-OpenROAD-Project/OpenROAD
Reproduces an OpenROAD GitHub bug from an attached tarball and shrinks the failing design with whittle.py so maintainers get a minimal test case.
Triage Issue
softspark/ai-toolkit
Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan.
Issue Triage Workflow
Hack23/cia
Triage GitHub issues: labeling, prioritization, assignment, and resolution tracking
More from ClickHouse/clickhouse-java
Write Doc Examples
ClickHouse/clickhouse-java
Write, rewrite, and format documentation code snippets into reusable, production-ready methods with necessary library imports and clean linting.
Update Keyword Engine Lists
ClickHouse/clickhouse-java
Update ALLOWEDKEYWORDALIASES in ClickHouseSqlUtils.java and ENGINETOTABLETYPE in DatabaseMetaDataImpl.java from failing test output.
Code Review
ClickHouse/clickhouse-java
Review changes in clickhouse-java for correctness, compatibility, API stability, and missing tests.
Related
Works with
Categories
Questions about Triage Issues
What does Triage Issues do?
Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java. Triage Issues is an agent skill from ClickHouse/clickhouse-java. Analyzes a single GitHub issue at a time.
When should I use Triage Issues?
Triage Issues fits situations like: the user asks to triage an issue; analyze a bug report; categorize a GitHub issue.
How do I install Triage Issues in Claude Code?
Run `npx skills add ClickHouse/clickhouse-java --skill triage-issues -a claude-code`. Or copy the skill folder (.cursor/skills/triage-issues in ClickHouse/clickhouse-java) into .claude/skills/triage-issues in your project. Claude Code loads it when a task matches its description.
How do I install Triage Issues in Codex?
Run `npx skills add ClickHouse/clickhouse-java --skill triage-issues -a codex`. Or copy the skill folder (.cursor/skills/triage-issues in ClickHouse/clickhouse-java) into .agents/skills/triage-issues in your project. Codex loads it when a task matches its description.
Can I use Triage Issues 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 ClickHouse/clickhouse-java --skill triage-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triage-issues, .gemini/skills/triage-issues, .github/skills/triage-issues and .opencode/skills/triage-issues in your project.
What does Triage Issues need to run?
SKILL.md names no scripts, command-line tools or credentials: Triage Issues is instructions for the agent only.
Does Triage Issues 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 Triage Issues 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 Triage Issues use?
Triage Issues is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Triage Issues use?
About 904 tokens (SKILL.md is roughly 3.6k 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 Triage Issues?
Skills that share tags, products or a category with Triage Issues: Issue Triage (pnp/powershell, 905 stars), GitHub Issue Creator (aiskillstore/marketplace, 430 stars), Bug Report Triage (OrchestratorInc/agent-orchestrator, 13k stars) and OpenROAD Issue Triage (The-OpenROAD-Project/OpenROAD, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Triage Issues?
ClickHouse (a GitHub organization) maintains it in ClickHouse/clickhouse-java, which has 1,620 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.
Source: ClickHouse/clickhouse-java on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.