skills.rest
mhdxbilal
mhdxbilalCOMMUNITY
Explore all skills by this author →
GitHub

skill-issues

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

1|Updated Jun 12, 2026
Search Tags:#blockers#persistence#history#bugs#issue#tracking#cross-session
One-click install
npx skills add https://github.com/mhdxbilal/Ai --skill skill-issues-mhdxbilal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-issues
Source: https://github.com/mhdxbilal/Ai/tree/main/.claude/skills/skill-issues
Command: npx skills add https://github.com/mhdxbilal/Ai --skill skill-issues-mhdxbilal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track issues and blockers across Claude Code sessions with persistent memory.

Core Features & Use Cases

  • Cross-session issue tracking for open problems, blockers, and gaps.
  • Initialize and maintain a centralized issues log at .octo/ISSUES.md with open and resolved sections.
  • Subcommands for listing, adding, resolving, and showing issue details, with automated ID generation and pattern alerts.

Quick Start

Tell me to track an issue or list issues and I will manage a persistent cross-session issue log.

Frequently Asked Questions about skill-issues

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

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

Cross-session issue tracking works by storing bugs and blockers in a centralized .octo/ISSUES.md file, preserving existing entries while moving issues between Open and Resolved sections across workflows.

Can I maintain an issue log that persists after closing a coding session?▼

Yes, persistent issue tracking stores all open problems and gaps in .octo/ISSUES.md, allowing you to list, add, resolve, and view issue details across new sessions without losing history.

What's the best way to manage issue history for a coding project without losing previous entries?▼

Using a centralized issues log at .octo/ISSUES.md ensures issue history is preserved. It maintains existing entries and automatically moves resolved items to a dedicated section while keeping open issues active.

How to add and resolve issues with automated ID generation?▼

Use subcommands for adding and resolving issues to trigger automated ID generation and pattern alerts. The system initializes and maintains the log at .octo/ISSUES.md with distinct Open and Resolved sections.

Does cross-session issue tracking require external dependencies?▼

No external dependencies are required. The issue tracking operates independently, storing data directly in the .octo/ISSUES.md markdown file within your project directory to maintain issue history.

Related Skills

Explore More Software Engineering Skills→
adamrdrewadamrdrew
1

db-init

Create a database directory and empty index.md file idempotently.

Community
Intermediate
mvillmowmvillmow
18

track-implementation-progress

Track GitHub issue implementation progress and identify blockers by phase.

Community
Basic
mrgeoffrichmrgeoffrich
3

execute-next-task

Claim and execute next unblocked project ticket with environment setup and test runs.

Community
Advanced
whichguywhichguy

linear

Query and manage Linear issues, projects, and teams via GraphQL API.

Community
Advanced