skills.rest
burgebj
burgebjCOMMUNITY
Explore all skills by this author →
GitHub

skill-issues

Track project blockers and bugs in persistent issue records.

Updated Jun 16, 2026
Search Tags:#project management#claude code#blockers#issue tracking#triage#bug management
One-click install
npx skills add https://github.com/burgebj/claudeoctopus --skill skill-issues-burgebj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-issues
Source: https://github.com/burgebj/claudeoctopus/tree/main/.claude/skills/skill-issues
Command: npx skills add https://github.com/burgebj/claudeoctopus --skill skill-issues-burgebj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents recurring development problems from being forgotten by providing persistent issue tracking across Claude Code sessions.

Core Features & Use Cases

  • Issue Lifecycle Management: Create, list, inspect, and resolve tracked project issues with persistent records in.octo/ISSUES.md.
  • Structured Triage: Capture severity, category, project phase, resolution notes, and detect recurring issue patterns.
  • Use Case: When a team discovers a recurring integration blocker during development, use this Skill to record the issue, track progress, and preserve the resolution history for future sessions.

Quick Start

Use the skill-issues skill to list all current open project issues and show their status.

Frequently Asked Questions about skill-issues

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

FAQPage Schema
How do I track project blockers and bugs across Claude Code sessions?▼

Persistent issue tracking across Claude Code sessions is achieved by storing structured records in an ISSUES.md file. This captures severity, category, resolution notes, and detects recurring patterns for bug and blocker management.

What is the best way to manage issue triage and resolution history during software development?▼

Issue triage and resolution history management is handled by generating persistent records with unique IDs that capture severity, project phase, and resolution notes. This structured approach detects recurring issue patterns and preserves project history.

Can I classify bugs by severity and project phase using persistent issue records?▼

Yes, bugs and blockers can be classified by severity and project phase. The tracking system applies structured issue storage with severity classification, ID generation, and safe updates to persistent documentation.

How do I list and inspect current open project issues?▼

Listing and inspecting open project issues is performed by querying the persistent issue documentation. This retrieves current blockers and their status, allowing teams to review project history and track progress.

Does issue tracking work without external dependencies or project management platforms?▼

Yes, issue tracking works without external dependencies by relying on persistent markdown documentation. It maintains structured issue storage, severity classification, and ID generation locally within the development environment.

When should I not use a local markdown file for bug management?▼

Local markdown bug management is not ideal for large-scale multi-team collaboration requiring real-time synchronization. It is designed for individual or small team workflows needing persistent issue records across development sessions.

Related Skills

Explore More Software Engineering Skills→
danielorzeata83-a11ydanielorzeata83-a11y

setup-matt-pocock-skills

Configure issue trackers and domain documentation for agent skills.

Community
Intermediate
dapperdiversdapperdivers
1

open-items-ledger

Maintains verified operational item tracking in a machine-readable JSON ledger.

Community
Advanced
amdmaxamdmax
2

bug-fix

Automate bug investigation, fixing, and regression testing from a GitHub backlog.

Community
Advanced
NourcineAbNourcineAb

github-project-management

Automate GitHub issue tracking, board synchronization, and sprint planning workflows.

Community
Advanced