issue-tracking

Creates, updates, and closes issues in trackers like GitHub, Jira, and Linear using structured templates.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/gnarea/clone --skill issue-tracking-gnarea
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-tracking
Source: https://github.com/gnarea/clone/tree/main/skills/issue-tracking
Command: npx skills add https://github.com/gnarea/clone --skill issue-tracking-gnarea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-structured issues and comments across different trackers is error-prone: duplicates get filed, bug reports lack reproduction steps, and tone drifts from the author's voice. This Skill enforces templates, deduplication checks, and sign-off rules for every tracker write operation. ## Core Features & Use Cases - Duplicate Detection: Searches open and closed issues before filing, adding comments or reopening matches instead of creating duplicates. - Structured Templates: Provides mandatory Markdown templates for bug reports (overview, current/expected behaviour, implementation details) and feature requests (problem, proposed solution, alternatives). - Tone and Sign-off Control: Applies the ghost-writing skill's semi-formal tone for issues and informal tone for comments, and requires explicit user sign-off before any write operation. - Use Case: When a user reports a crash, search GitHub for existing reports, draft a bug issue with reproduction steps and permalinks to the faulty code, present it for approval, then file it. ## Quick Start Ask the assistant to file a bug report on GitHub describing the problem you encountered, and it will check for duplicates, draft the issue using the standard template, and request your sign-off before submitting.

Frequently Asked Questions about issue-tracking

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

FAQPage Schema
How do I write a good bug report for GitHub issues?▼

A good bug report contains an overview summarizing the issue and impact, the current behaviour with reproduction steps, the expected behaviour, and optional implementation details. This Skill enforces that exact template and linkifies code references with GitHub permalinks.

How to avoid creating duplicate issues in an issue tracker?▼

Search the tracker for both open and closed issues before filing. If a match exists, add new information as a comment; if the match is closed, reopen it or file a follow-up instead of creating a duplicate.

Does this work with Jira and Linear or only GitHub?▼

The guidelines apply to any issue tracker, including GitHub, Jira, and Linear. Tracker-specific conventions like closing as "not planned" are mapped to each tracker's equivalent status.

Can the AI file an issue without my approval?▼

No. The Skill requires explicit user sign-off before any write operation on the tracker. The drafted content is presented to you first unless you have instructed otherwise.

What tone should issue comments use compared to issue descriptions?▼

Issue descriptions use a semi-formal tone following the ghost-writing skill, while comments use an informal tone. Updates must preserve the issue's pre-existing language and structure, especially when the author differs from the current user.