issue-filing

Create and label GitHub issues and epics following kajet-turbo project conventions.

1|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/jpalczewski/kajet-turbo --skill issue-filing-jpalczewski
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-filing
Source: https://github.com/jpalczewski/kajet-turbo/tree/main/.claude/skills/issue-filing
Command: npx skills add https://github.com/jpalczewski/kajet-turbo --skill issue-filing-jpalczewski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Filing GitHub issues inconsistently — wrong prefixes, missing labels, no board placement, untracked dependencies — fragments a project's backlog and makes triage impossible. This Skill enforces kajet-turbo's established conventions so every issue lands correctly typed, labeled, and placed on the project board. ## Core Features & Use Cases - Convention-driven filing: Maps title prefixes (fix:, feat:, epic:, risk:, etc.) to the correct type labels and body templates (Problem/Impact/Proposal/Acceptance, or Options for open questions). - Board and dependency management: Adds every issue to the "Kajet Turbo" project board in Inbox, creates native blocked-by links, and wires epic sub-issues with ordering and dependency tracking. - Use Case: After a code review uncovers an out-of-scope bug, use this Skill to file a properly prefixed fix: issue with a provenance trailer, the right label, board placement, and a blocked-by link to the related work. ## Quick Start File a new GitHub issue for the bug we just found in the search chunking logic, following the issue-filing conventions.

Frequently Asked Questions about issue-filing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub issue with the gh CLI and add it to a project board?▼

Use gh issue create with the --project flag, for example gh issue create ... --project "Kajet Turbo". For an existing issue, use gh issue edit N --add-project "Kajet Turbo" — note the flag name differs between the two subcommands.

How do I link blocking dependencies between GitHub issues?▼

Use native blocked-by relationships: gh issue edit A --add-blocked-by B, or --blocked-by B at creation time. This creates a real GitHub relationship that is filterable, queryable via the API, and clears automatically when the blocking issue closes.

How do I create an epic tracking issue with sub-issues on GitHub?▼

Create an issue titled epic: <name> with an Order checklist and Dependencies section in the body, then attach children with gh issue edit <epic> --add-sub-issue <N> or gh issue create --parent <epic>. The body remains the authoritative sequencing since sub-issues carry no ordering semantics.

Should I set a priority when filing a new GitHub issue?▼

No. New issues land in Inbox with no priority — the filer sees one issue while triage weighs it against the whole board. Priority is set later during backlog triage via the board's Priority field, not at filing time.

What should I do before publishing an issue that contains production data?▼

Anonymize any real note content, queries, or names per the project's CLAUDE.local.md rules before running gh issue create or edit. Afterward, run gh issue view N --json body and read the full published body back to verify nothing sensitive leaked.