issue-tracking

Create and update epics, stories, tasks, bugs, and comments in file system or GitHub repositories.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/dragoscirjan/opencode-config --skill issue-tracking-dragoscirjan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-tracking
Source: https://github.com/dragoscirjan/opencode-config/tree/main/skills/issue-tracking
Command: npx skills add https://github.com/dragoscirjan/opencode-config --skill issue-tracking-dragoscirjan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the confusion of managing development work across different issue backends by standardizing how epics, stories, tasks, bugs, and comments are created and updated.

Core Features & Use Cases

  • Backend Detection: Uses the ISSUE_TRACKING setting to determine whether work lives in the file system or on GitHub.
  • Issue Lifecycle Management: Supports structured creation and updates for initiatives, epics, stories, tasks, and bugs.
  • Consistent Communication: Enforces Gherkin-based issue bodies and a standardized comment format for clear progress reporting.
  • Use Case: A team member needs to open a new story, link it to a parent epic, and post progress updates without manually formatting each issue.

Quick Start

Use the issue-tracking skill to inspect the current ISSUE_TRACKING setting and create or update the appropriate issue in the configured system.

Frequently Asked Questions about issue-tracking

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

FAQPage Schema
How do I track GitHub issues and epics from the local file system?

Issue tracking supports both local file system and GitHub backends by reading the ISSUE_TRACKING setting to determine storage. It standardizes creation and updates for epics, stories, tasks, and bugs across your configured repository environment.

Can I use Gherkin syntax for issue tracking bodies and comments?

Gherkin syntax is enforced for issue bodies to ensure structured, clear communication. The skill formats issue bodies and comments to match your repository’s specific templates, standardizing progress reporting across development tasks.

How do I create a story and link it to a parent epic automatically?

Creating a story and linking it to a parent epic is handled through hierarchy management features. The skill selects the correct storage tools based on your ISSUE_TRACKING configuration to create and update linked records seamlessly.

Does this issue tracking method work without external dependencies?

Yes, the skill operates with no external dependencies. It relies solely on reading the ISSUE_TRACKING setting to interact with either your local file system or GitHub repository for issue lifecycle management.

What is the best way to standardize bug tracking across different backends?

Standardizing bug tracking across backends is achieved by applying consistent Gherkin-based bodies and standardized comment formats. The skill removes backend confusion by uniformly managing status updates and hierarchy across file systems and GitHub.

Why does my issue update fail to match the repository template?

Issue updates require formatting bodies and comments to the repository’s specific issue and comment templates. The skill automatically applies these template formats to ensure your task and bug updates are correctly structured.