skills.rest
tardyp
tardypCOMMUNITY
Explore all skills by this author →
GitHub

issue_tracking

Create and track software issues with severity, type, and status.

Updated Feb 10, 2026
Search Tags:#project management#development workflow#issue tracking#traceability#tech debt#bug tracking
One-click install
npx skills add https://github.com/tardyp/esp_tock --skill issue-tracking-tardyp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue_tracking
Source: https://github.com/tardyp/esp_tock/tree/main/.opencode/skills/issue_tracking
Command: npx skills add https://github.com/tardyp/esp_tock --skill issue-tracking-tardyp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured system for tracking project issues, bugs, and technical debt, ensuring clarity and accountability in development workflows.

Core Features & Use Cases

  • Issue Creation: Define new issues with severity, type, and sprint assignment.
  • Status Tracking: Monitor the lifecycle of issues from open to resolved.
  • Tech Debt Management: Log and track technical debt for future sprints.
  • Use Case: A developer encounters a bug during testing. They use this Skill to create a new 'bug' issue, assign it a 'high' severity, and link it to the current sprint for immediate attention.

Quick Start

Use the issue_tracking skill to create a new bug issue with the title "Fix login button alignment".

Frequently Asked Questions about issue_tracking

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

FAQPage Schema
How do I track technical debt and bugs in a software development workflow?▼

To track technical debt and bugs in a software development workflow, you can create categorized issues with defined severity levels, issue types, and sprint assignments to monitor their lifecycle from open to resolved.

What is the best way to maintain traceability for project issues and bugs?▼

Maintaining traceability for project issues involves logging bugs and technical debt in a global tracker and integrating their references directly into commit messages and development reports.

How do I categorize and assign severity levels to development issues?▼

Categorizing development issues requires defining specific issue types, assigning severity levels, and linking the items to current or future sprints to ensure clear prioritization and accountability.

Can I integrate issue tracking with commit messages for better project quality?▼

Yes, this issue tracking approach supports integration with commit messages and reports, ensuring clear issue referencing that maintains project quality and accountability across development workflows.

Does this issue tracking method work for managing tech debt in future sprints?▼

Yes, this method works for managing tech debt by allowing developers to log technical debt issues and explicitly track them for assignment and resolution in future development sprints.

Related Skills

Explore More Software Engineering Skills→
koolamusickoolamusic
9

kickoff

Initialize project structures and workflow documentation for software repositories.

Community
Advanced
jmaglyjmagly
175

sdlc-reports

Generate SDLC reports with iteration status, metrics dashboards, and executive summaries.

Community
Advanced
pegasus-isipegasus-isi

commit

Generate Conventional Commits from git status, diffs, and branch metadata.

Official
Intermediate
qauth-labsqauth-labs
23

gh-issues

Automate GitHub issue creation, viewing, editing, and lifecycle management.

Official
Intermediate