skills.rest
nyldn
nyldnCOMMUNITY
Explore all skills by this author →
Website𝕏@nyldnGitHub

skill-issues

Track and persist issues across Claude Code sessions in .octo/ISSUES.md.

4.0k|369|Updated Jan 15, 2026
Search Tags:#workflow#blockers#issues#state-management#persist#track
One-click install
npx skills add https://github.com/nyldn/claude-octopus --skill skill-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-issues
Source: https://github.com/nyldn/claude-octopus/tree/main/skills/skill-issues
Command: npx skills add https://github.com/nyldn/claude-octopus --skill skill-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-session issue tracking for persistent problem management. Issues are stored in .octo/ISSUES.md and survive across Claude Code sessions.

Core principle: Track → Resolve → Learn.

Core Features & Use Cases

  • List Issues (Open Issues table) and view categories, severities, and phases.
  • Add Issue to create a new entry with an auto-generated ID.
  • Resolve Issue to move it to the Resolved section with resolution notes.
  • Show Issue Details for any specific issue across Open and Resolved sections.

Quick Start

Create a new issue to track a blocker across sessions, then list, show, and resolve issues as work progresses.

Frequently Asked Questions about skill-issues

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

FAQPage Schema
How do I track blockers and issues across multiple Claude Code sessions?▼

Persistent issue tracking across Claude Code sessions is achieved by recording blockers in a markdown file. This skill writes issues to .octo/ISSUES.md, ensuring your problem log survives session restarts.

What is the best way to maintain a persistent problem log for software engineering workflows?▼

A persistent problem log requires writing issues to a file that persists across sessions. This skill manages .octo/ISSUES.md to track open and resolved items with unique IDs and aging schemes.

How do I resolve an issue and move it to a resolved view in my tracking workflow?▼

To resolve an issue, this skill moves the entry from the Open Issues table to the Resolved section in .octo/ISSUES.md. You can add resolution notes during this process to document the fix.

Can I review open issues and their categories across different Claude sessions?▼

Yes, you can review open issues across sessions by listing entries from the .octo/ISSUES.md file. The skill displays categories, severities, and phases for each tracked blocker.

Does this issue tracking method require any external dependencies or components?▼

No external dependencies or components are required for this issue tracking method. It relies solely on reading and writing to a local markdown file at .octo/ISSUES.md.

When should I use a markdown-based issue tracker instead of a dedicated state-management tool?▼

Use a markdown-based issue tracker when you need a lightweight, cross-session problem log without external databases. It is ideal for tracking blockers, generating unique IDs, and maintaining open and resolved views.

Related Skills

Explore More Software Engineering Skills→
iVintikiVintik

issues

Log and track plugin issues in a structured ISSUES.md file.

Community
Intermediate
ChoiHyunjinChoiHyunjin

end-web

Summarize web project session changes, tasks, and pending actions in markdown.

Community
Intermediate
burgebjburgebj

skill-resume

Restores interrupted project sessions from saved workflow state and metadata.

Community
Advanced
alangebalangeb

plan_template

Generate structured Markdown plan files with an 8-section template.

Community
Intermediate