Link Ticket To Session
JayantDevkar/claude-code-karma
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma.
Creates a GitHub issue or JIRA ticket for a YugabyteDB change or bug, after scrubbing customer data, secrets and unreleased details from anything public.
Install YugabyteDB Issue Creator
$ npx skills add yugabyte/yugabyte-db --skill create-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yugabyte/yugabyte-db create-issue --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/yugabyte/yugabyte-db.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/create-issue .claude/skills/create-issue && 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 "create-issue" agent skill from https://github.com/yugabyte/yugabyte-db/tree/master/.claude/skills/create-issue into .claude/skills/create-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-issue", 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/yugabyte/yugabyte-db/tree/master/.claude/skills/create-issueType 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 yugabyte/yugabyte-db --skill create-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yugabyte/yugabyte-db create-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yugabyte/yugabyte-db.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/create-issue .agents/skills/create-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-issue" agent skill from https://github.com/yugabyte/yugabyte-db/tree/master/.claude/skills/create-issue into .agents/skills/create-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-issue", 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 yugabyte/yugabyte-db --skill create-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yugabyte/yugabyte-db create-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yugabyte/yugabyte-db.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/create-issue .cursor/skills/create-issue && 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 "create-issue" agent skill from https://github.com/yugabyte/yugabyte-db/tree/master/.claude/skills/create-issue into .cursor/skills/create-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-issue", 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/yugabyte/yugabyte-db.git --path .claude/skills/create-issue--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 yugabyte/yugabyte-db --skill create-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yugabyte/yugabyte-db create-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yugabyte/yugabyte-db.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/create-issue .gemini/skills/create-issue && 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 "create-issue" agent skill from https://github.com/yugabyte/yugabyte-db/tree/master/.claude/skills/create-issue into .gemini/skills/create-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-issue", 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 yugabyte/yugabyte-db create-issueInstalls 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 yugabyte/yugabyte-db --skill create-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yugabyte/yugabyte-db.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/create-issue .github/skills/create-issue && 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 "create-issue" agent skill from https://github.com/yugabyte/yugabyte-db/tree/master/.claude/skills/create-issue into .github/skills/create-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-issue", 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 yugabyte/yugabyte-db --skill create-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yugabyte/yugabyte-db create-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yugabyte/yugabyte-db.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/create-issue .opencode/skills/create-issue && 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 "create-issue" agent skill from https://github.com/yugabyte/yugabyte-db/tree/master/.claude/skills/create-issue into .opencode/skills/create-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-issue", 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
create-issue- GitHub stars
- 11k
- Token cost
- ~2k tokens
- SKILL.md length
- 994 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Creates a GitHub issue or JIRA ticket for a YugabyteDB change or bug, after scrubbing customer data, secrets and unreleased details from anything public.
- Works in 3 steps: Decide the tracker — GitHub vs JIRA → Gather title metadata → Report back
- Filing a bug report for YugabyteDB
- SKILL.md covers Confidentiality — read before…, Prerequisites, Workflow and Notes
- Calls gh and git
What it does
This skill files a tracking issue and returns its number or JIRA key, so it can feed the create-pr or create-diff steps. A GitHub issue in yugabyte/yugabyte-db is the default for core database code, while a JIRA ticket is the default for YBA and platform work. It is used when no tracker reference exists yet, either before opening a PR or diff or for a standalone bug or feature request.
A long confidentiality section comes first because GitHub issues are public and permanent. Titles, bodies and labels must not contain customer-identifying data, personal information, unanonymized customer schemas or queries, secrets and credentials, or non-public YugabyteDB information such as an unreleased roadmap. Customer reports are read from internal sources with only internal ticket IDs referenced, and a minimal synthetic reproducer replaces real tables and queries. If something might be sensitive, the agent asks you instead of writing it. The allowed tools are gh issue create, gh issue view, gh auth status and Read.
When your agent uses it
- Filing a bug report for YugabyteDB
- Getting a tracker reference before opening a PR
- Turning a customer report into a public issue without leaking customer details
Example prompts
- “File a GitHub issue for this tablet server crash and scrub anything customer-specific.”
- “Create a JIRA ticket for the platform upgrade bug we just found.”
- “I need an issue number for this change before I open the PR.”
Requirements
- GitHub CLI (gh), authenticated, for GitHub issues
- Pre-approved tools (allowed-tools): Bash(gh issue create *), Bash(gh issue view *), Bash(gh auth status), Read
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Decide the tracker — GitHub vs JIRA
- Gather title metadata
- Report back
What it can do on your machine
Read from SKILL.md and the folder at commit cdf582d. 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:
Bash(gh issue create *)Bash(gh issue view *)Bash(gh auth status)Read
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
cli.github.com
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
YugabyteDB Issue Creator loads about 2k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 994 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 994 words (~1,970 tokens).
“Create a tracking issue for a YugabyteDB change: either a GitHub issue in yugabyte/yugabyte-db (the default for core DB code) or a JIRA ticket (the default for YBA/platform work). Return the resulting issue number / JIRA key so it can…”
- name
- create-issue
- allowed-tools
- Bash(gh issue create *), Bash(gh issue view *), Bash(gh auth status), Read
- model
- sonnet
Files
Just SKILL.md in .claude/skills/create-issue of yugabyte/yugabyte-db.
Open the folder on GitHubat commit cdf582d
Compare with similar skills
YugabyteDB Issue Creator 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 |
|---|---|---|---|---|---|---|
| YugabyteDB Issue Creator this skillyugabyte/yugabyte-db | 11k | — | ~2k | Automated safety check: Pass | Custom licence | |
| Link Ticket To SessionJayantDevkar/claude-code-karma | 329 | — | ~1.8k | Automated safety check: Notes | Apache-2.0 | |
| Issue Triage Loopcobusgreyling/loop-engineering | 11k | — | ~522 | Automated safety check: Pass | MIT | |
| Leanspeccodervisor/leanspec | 296 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Triagebholmesdev/hubble.md | 1.5k | — | ~1.5k | Automated safety check: Pass | MIT | |
| PRP Implementation PlannerWirasm/prp | 2.3k | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
Issue Triage Loop
cobusgreyling/loop-engineering
Scans open GitHub issues and discussions, flags duplicates, scores priority and proposes labels into issue-triage-state.md without ever labeling or closing.
Leanspec
codervisor/leanspec
The spec-coding methodology for AI-assisted development. An agent skill from codervisor/leanspec.
Triage
bholmesdev/hubble.md
Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related issues, then return a structured decision with exactly one triage state.
PRP Implementation Planner
Wirasm/prp
Turns a PRD, issue or description into an implementation-ready plan grounded in codebase evidence, adding root-cause analysis for bugs and publishing issue plans back to the issue.
Dynamo PR Description
DynamoDS/Dynamo
Generate PR descriptions for Dynamo that align with the team template section names and order.
More from yugabyte/yugabyte-db
YugabyteDB ASH Instrumentation
yugabyte/yugabyte-db
Procedure for adding or changing YugabyteDB Active Session History wait states in TServer and DocDB C++ code, including the macro to use for sync and async paths.
YugabyteDB Phorge Diff Creator
yugabyte/yugabyte-db
Creates a Phorge code review diff for the current branch with arc diff, while applying public-repo confidentiality rules since Phorge content later lands verbatim on the public GitHub repo.
YugabyteDB Backport Review
yugabyte/yugabyte-db
Checks a YugabyteDB backport revision on Phorge against the original diff it was ported from and flags differences, tracing unexplained code back to master.
YBA Read-Only Query CLI
yugabyte/yugabyte-db
Runs read-only lookups - list, describe, get - against a live YugabyteDB Anywhere control plane using the yba CLI, with mutating commands explicitly off-limits.
Create Fork Pull Request
yugabyte/yugabyte-db
Pushes the current branch to your fork and opens a cross-repository GitHub pull request, with a strict check against leaking customer data into public text.
cargo-pgrx Commands and Tests
yugabyte/yugabyte-db
Helps choose and run cargo-pgrx commands and decide whether a Rust test is a plain test or a pg_test, so code never crosses the Postgres boundary the wrong way.
Related
Categories
Questions about YugabyteDB Issue Creator
What does YugabyteDB Issue Creator do?
Creates a GitHub issue or JIRA ticket for a YugabyteDB change or bug, after scrubbing customer data, secrets and unreleased details from anything public. This skill files a tracking issue and returns its number or JIRA key, so it can feed the create-pr or create-diff steps. A GitHub issue in yugabyte/yugabyte-db is the default for core database code, while a JIRA ticket is the default for YBA and platform work.
When should I use YugabyteDB Issue Creator?
YugabyteDB Issue Creator fits situations like: filing a bug report for YugabyteDB; getting a tracker reference before opening a PR; turning a customer report into a public issue without leaking customer details.
How do I install YugabyteDB Issue Creator in Claude Code?
Run `npx skills add yugabyte/yugabyte-db --skill create-issue -a claude-code`. Or copy the skill folder (.claude/skills/create-issue in yugabyte/yugabyte-db) into .claude/skills/create-issue in your project. Claude Code loads it when a task matches its description.
How do I install YugabyteDB Issue Creator in Codex?
Run `npx skills add yugabyte/yugabyte-db --skill create-issue -a codex`. Or copy the skill folder (.claude/skills/create-issue in yugabyte/yugabyte-db) into .agents/skills/create-issue in your project. Codex loads it when a task matches its description.
Can I use YugabyteDB Issue Creator 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 yugabyte/yugabyte-db --skill create-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/create-issue, .gemini/skills/create-issue, .github/skills/create-issue and .opencode/skills/create-issue in your project.
What does YugabyteDB Issue Creator need to run?
Going by SKILL.md and its folder, YugabyteDB Issue Creator needs the command-line tools its instructions call (gh and git). Our summary lists: GitHub CLI (gh), authenticated, for GitHub issues. Its frontmatter pre-approves these tools: Bash(gh issue create *), Bash(gh issue view *), Bash(gh auth status), Read.
Does YugabyteDB Issue Creator access the network?
SKILL.md names 1 domain. As links in the text: cli.github.com. This is read from the text; nothing was executed.
Is YugabyteDB Issue Creator 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 YugabyteDB Issue Creator use?
YugabyteDB Issue Creator 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 YugabyteDB Issue Creator use?
About 2k tokens (SKILL.md is roughly 7.9k 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 YugabyteDB Issue Creator?
Skills that share tags, products or a category with YugabyteDB Issue Creator: Link Ticket To Session (JayantDevkar/claude-code-karma, 329 stars), Issue Triage Loop (cobusgreyling/loop-engineering, 11k stars), Leanspec (codervisor/leanspec, 296 stars) and Triage (bholmesdev/hubble.md, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains YugabyteDB Issue Creator?
yugabyte (a GitHub organization) maintains it in yugabyte/yugabyte-db, which has 10,580 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.
Source: yugabyte/yugabyte-db on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.