Verified:GitHub

issue-tracking

Create, query, update, and close issues across GitHub, GitLab, Jira, Azure DevOps, and Linear.

18|9|Updated Apr 8, 2026

Search Tags:#ticket management #Linear #GitHub #issue tracking #Jira #work log #bug reporting

One-click install

npx skills add https://github.com/arozumenko/sdlc-skills --skill issue-tracking-arozumenko

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: issue-tracking
Source: https://github.com/arozumenko/sdlc-skills/tree/main/skills/issue-tracking
Command: npx skills add https://github.com/arozumenko/sdlc-skills --skill issue-tracking-arozumenko

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of taking an issue idea (bug, task, or epic) and consistently turning it into the right ticket in the right tracker with the right update workflow.

Core Features & Use Cases

Tracker-aware dispatch: Creates, queries, comments, updates, and closes tickets across GitHub, GitLab, Jira, Azure DevOps, and Linear based on your project’s configured issue tracker.
Bug/task/epic templates: Uses shared body templates for consistent ticket quality, including bug-report structure and workflow state discipline.
Operational audit trail: Posts consistent work-log comment prefixes for started, progress, blocked, done, testing, and verification events.

Quick Start

Tell the AI IDE to file a bug using the project’s configured issue tracker and return the created ticket ID and URL.

Frequently Asked Questions about issue-tracking

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

FAQPage Schema

How do I automate issue tracking across multiple platforms like Jira and GitHub?▼

Automate issue tracking across Jira, GitHub, GitLab, Azure DevOps, and Linear using tracker-aware dispatch to consistently create, query, update, and close tickets. The skill selects the destination automatically and applies structured templates for bugs, tasks, and epics.

Can I file and update bug reports in Linear from an AI IDE?▼

Yes, you can file and update bug reports in Linear by instructing your AI IDE to create the ticket using your project's configured issue tracker. The skill returns the created ticket ID and URL while applying consistent bug-report structure templates.

Does issue tracking work with both GitHub and Azure DevOps without changing workflows?▼

Yes, issue tracking works with GitHub and Azure DevOps without changing workflows by using tracker-aware dispatch. It translates filing bugs, creating tasks, and posting progress into consistent operations across whichever tracker is configured in your project profile.

What is the best way to post progress updates and work logs to existing tickets?▼

The best way to post progress updates and work logs to existing tickets is using standardized comment prefixes for started, progress, blocked, done, testing, and verification events. This maintains an operational audit trail across GitHub, Jira, GitLab, Linear, and Azure DevOps.

Do I need specific CLI tools installed to create tickets in Jira or Linear?▼

Yes, you need the corresponding tracker's CLI or MCP tools installed and wired by the calling agent to create tickets in Jira or Linear. The skill requires these dependencies to execute commands and select the correct destination from your project profile.

Why use automated ticket templates for bug reporting instead of manual entry?▼

Automated ticket templates for bug reporting ensure consistent ticket quality and workflow state discipline across multiple trackers. Instead of manual entry, the skill applies shared body templates to standardize issue data, reducing formatting errors and missing context.