Exposed Bug Fix Workflow
JetBrains/Exposed
Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.
Verify a GitHub issue against current code and related pull requests.
Install Issue Validator
$ npx skills add caarlos0/dotfiles --skill issue-validator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install caarlos0/dotfiles issue-validator --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/caarlos0/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/issue-validator .claude/skills/issue-validator && 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 "issue-validator" agent skill from https://github.com/caarlos0/dotfiles/tree/main/skills/issue-validator into .claude/skills/issue-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-validator", 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/caarlos0/dotfiles/tree/main/skills/issue-validatorType 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 caarlos0/dotfiles --skill issue-validator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install caarlos0/dotfiles issue-validator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caarlos0/dotfiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/issue-validator .agents/skills/issue-validator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issue-validator" agent skill from https://github.com/caarlos0/dotfiles/tree/main/skills/issue-validator into .agents/skills/issue-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-validator", 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 caarlos0/dotfiles --skill issue-validator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install caarlos0/dotfiles issue-validator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caarlos0/dotfiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/issue-validator .cursor/skills/issue-validator && 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 "issue-validator" agent skill from https://github.com/caarlos0/dotfiles/tree/main/skills/issue-validator into .cursor/skills/issue-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-validator", 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/caarlos0/dotfiles.git --path skills/issue-validator--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 caarlos0/dotfiles --skill issue-validator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install caarlos0/dotfiles issue-validator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caarlos0/dotfiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/issue-validator .gemini/skills/issue-validator && 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 "issue-validator" agent skill from https://github.com/caarlos0/dotfiles/tree/main/skills/issue-validator into .gemini/skills/issue-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-validator", 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 caarlos0/dotfiles issue-validatorInstalls 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 caarlos0/dotfiles --skill issue-validator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/caarlos0/dotfiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/issue-validator .github/skills/issue-validator && 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 "issue-validator" agent skill from https://github.com/caarlos0/dotfiles/tree/main/skills/issue-validator into .github/skills/issue-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-validator", 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 caarlos0/dotfiles --skill issue-validator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install caarlos0/dotfiles issue-validator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caarlos0/dotfiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/issue-validator .opencode/skills/issue-validator && 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 "issue-validator" agent skill from https://github.com/caarlos0/dotfiles/tree/main/skills/issue-validator into .opencode/skills/issue-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-validator", 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
issue-validator- GitHub stars
- 220
- Token cost
- ~266 tokens
- SKILL.md length
- 125 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- MIT
At a glance
Verify a GitHub issue against current code and related pull requests.
- Works in 6 steps: Fetch the issue, comments, labels, and… → Resolve the target branch and inspect… → Translate stale paths, symbols, and line… → …
- Is this still true? investigations
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Pull requests
What it does
Issue Validator is an agent skill from caarlos0/dotfiles. Verify a GitHub issue against current code and related pull requests. Use for issue triage, stale reports, duplicates, regressions, or "is this still true?" investigations.
Its SKILL.md is about 270 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 Pull requests and Issue triage. It works with GitHub. The licence is MIT.
When your agent uses it
- Is this still true? investigations
- Tasks that involve Pull requests
- Tasks that involve Issue triage
Example prompts
- “is this still true?”
- “/issue-validator”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Fetch the issue, comments, labels, and referenced pull requests with gh.
- Resolve the target branch and inspect its current code, not only the issue's
- Translate stale paths, symbols, and line numbers through renames or ports.
- Trace the reachable user path and reproduce the behavior when practical.
- Search open and merged pull requests plus recent history for fixes,
- Classify the issue as valid, partially valid, fixed, duplicate,
What it can do on your machine
Read from SKILL.md and the folder at commit b144097. 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
Issue Validator loads about 266 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 125 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 caarlos0/dotfiles at commit b144097, republished under its MIT licence (© caarlos0). 125 words, ~266 tokens.
Download SKILL.mdSave it as
.claude/skills/issue-validator/SKILL.md (or your agent's skills folder).- name
- issue-validator
- description
- Verify a GitHub issue against current code and related pull requests. Use for issue triage, stale reports, duplicates, regressions, or "is this still true?" investigations.
Issue Validator
Validate before proposing or making a fix.
- Fetch the issue, comments, labels, and referenced pull requests with
gh. - Resolve the target branch and inspect its current code, not only the issue's cited revision.
- Translate stale paths, symbols, and line numbers through renames or ports.
- Trace the reachable user path and reproduce the behavior when practical.
- Search open and merged pull requests plus recent history for fixes, regressions, duplicates, and conflicting changes.
- Classify the issue as
valid,partially valid,fixed,duplicate,superseded, ornot reproducible.
Separate confirmed facts from hypotheses. A code smell in an unreachable path does not validate an issue. Do not edit by default; end with the smallest justified next action and current file/symbol references.
© caarlos0, MIT. 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 skills/issue-validator of caarlos0/dotfiles.
Open the folder on GitHubat commit b144097
Compare with similar skills
Issue Validator 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 |
|---|---|---|---|---|---|---|
| Issue Validator this skillcaarlos0/dotfiles | 220 | — | ~266 | Automated safety check: Pass | MIT | |
| Exposed Bug Fix WorkflowJetBrains/Exposed | 9.3k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Ouroboros Maintainer TriageQ00/ouroboros | 6.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| PR Triagertk-ai/rtk | 83k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Read-Only GitHub Triagecode-yeongyu/oh-my-openagent | 70k | — | ~4.3k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
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.
Ouroboros Maintainer Triage
Q00/ouroboros
Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change.
PR Triage
rtk-ai/rtk
Audits a repository's open pull requests, deep-reviews chosen ones and drafts review comments that are only posted after you approve them.
Read-Only GitHub Triage
code-yeongyu/oh-my-openagent
Fans out one background subagent per open GitHub issue or pull request to write an evidence-backed report, never commenting, closing or merging anything.
Qwen Code Issue and PR Triage
QwenLM/qwen-code
Gatekeeps GitHub issues and pull requests for Qwen Code maintainers through staged static reviews that post a comment after each stage, under strict safety rules.
More from caarlos0/dotfiles
All 20 skills in this repoCLI Design
caarlos0/dotfiles
Design and review command-line interfaces for usability, automation, safety, accessibility, and long-term compatibility.
Dependabot Merge
caarlos0/dotfiles
Review and merge open dependency pull requests from Dependabot, Renovate and similar bots across the goreleaser organization and the caarlos0 user.
Gh CLI
caarlos0/dotfiles
Use GitHub CLI efficiently for pull requests, CI checks, workflow runs, logs, and merge status.
Tui Design
caarlos0/dotfiles
Design terminal user interfaces and interactive CLIs that stay usable, accessible, and scriptable.
Dashboard
caarlos0/dotfiles
Design and review dashboards that are informative, honest, accessible, and visually polished, independent of any tool.
Gh Doc Author
caarlos0/dotfiles
Author and revise clear GitHub internal documentation, including design docs, proposals, decision records, runbooks, status updates, and handoffs.
Related
Works with
Categories
Questions about Issue Validator
What does Issue Validator do?
Verify a GitHub issue against current code and related pull requests. Issue Validator is an agent skill from caarlos0/dotfiles. Verify a GitHub issue against current code and related pull requests.
When should I use Issue Validator?
Issue Validator fits situations like: is this still true? investigations; tasks that involve Pull requests; tasks that involve Issue triage.
How do I install Issue Validator in Claude Code?
Run `npx skills add caarlos0/dotfiles --skill issue-validator -a claude-code`. Or copy the skill folder (skills/issue-validator in caarlos0/dotfiles) into .claude/skills/issue-validator in your project. Claude Code loads it when a task matches its description.
How do I install Issue Validator in Codex?
Run `npx skills add caarlos0/dotfiles --skill issue-validator -a codex`. Or copy the skill folder (skills/issue-validator in caarlos0/dotfiles) into .agents/skills/issue-validator in your project. Codex loads it when a task matches its description.
Can I use Issue Validator 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 caarlos0/dotfiles --skill issue-validator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-validator, .gemini/skills/issue-validator, .github/skills/issue-validator and .opencode/skills/issue-validator in your project.
What does Issue Validator need to run?
SKILL.md names no scripts, command-line tools or credentials: Issue Validator is instructions for the agent only.
Does Issue Validator 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 Issue Validator 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 Issue Validator use?
Issue Validator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Issue Validator use?
About 266 tokens (SKILL.md is roughly 1.1k 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 Issue Validator?
Skills that share tags, products or a category with Issue Validator: Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars), Pre-Release PR Triage (jamiepine/voicebox, 57k stars), Ouroboros Maintainer Triage (Q00/ouroboros, 6.2k stars) and PR Triage (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Issue Validator?
caarlos0 (a GitHub user) maintains it in caarlos0/dotfiles, which has 220 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 7, 2026.
Source: caarlos0/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.