skills.rest
iVintik
iVintikCOMMUNITY
Explore all skills by this author →
GitHub

issues

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

Updated Feb 22, 2026
Search Tags:#workflow#debugging#markdown#plugin#issues#tracking#issuemanagement
One-click install
npx skills add https://github.com/iVintik/claude-plugin-ops --skill issues-ivintik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issues
Source: https://github.com/iVintik/claude-plugin-ops/tree/main/skills/issues
Command: npx skills add https://github.com/iVintik/claude-plugin-ops --skill issues-ivintik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track bugs and problems in a local ISSUES.md file. Use when the user wants to log, note, or record a problem for later — not fix it now. Also use for: listing what's currently tracked, marking an ISSUE-NNN as resolved, or updating issue status.

Core Features & Use Cases

  • Initialize an ISSUES.md file at the plugin root to start tracking issues.
  • List all tracked issues with IDs, statuses, severities, and descriptions.
  • Add new issues with a structured format, including title, context, and description, and mark issues as resolved or updated.
  • Manage issue lifecycle by resolving and updating existing entries through a standardized workflow.

Quick Start

Initialize ISSUES.md at the plugin root and log a new issue.

Frequently Asked Questions about issues

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

FAQPage Schema
How do I track plugin bugs and issues in a local markdown file?▼

You can track plugin bugs in a local markdown file by initializing an ISSUES.md file at the plugin root. This structured file logs problems with IDs, statuses, and descriptions for later resolution.

What is the best way to log development problems for later resolution?▼

Logging development problems for later resolution involves adding new entries to a structured ISSUES.md file. This records the title, context, and description without immediately fixing the issue.

How do I initialize and manage an issue tracking workflow in markdown?▼

To initialize an issue tracking workflow in markdown, create an ISSUES.md file at the plugin root. You can then list tracked issues, add new problems, update issue status, and mark entries as resolved.

Can I update issue status and mark tracked problems as resolved in ISSUES.md?▼

Yes, you can update issue status and mark tracked problems as resolved in ISSUES.md. The workflow supports managing the issue lifecycle through standardized updates to existing entries.

Does this issue management approach require external dependencies or databases?▼

This issue management approach does not require external dependencies or databases. It operates by applying structured updates directly to a local ISSUES.md file to capture and organize problems.

When should I use a local ISSUES.md file instead of immediately fixing bugs?▼

Use a local ISSUES.md file when you want to capture, organize, and note a problem for later rather than fixing it immediately. It is ideal for tracking issue lifecycles during ongoing plugin development.

Related Skills

Explore More Software Engineering Skills→
PixelSculptorPixelSculptor

10x-init

Create a project context directory with change tracking, archiving, and documentation files.

Community
Basic
semicolon-devteamsemicolon-devteam

iteration-tracker

Track test iterations and outcomes for GitHub issues via issue comments.

Official
Advanced
aresbitaresbit
46

obsidian

Automate Obsidian vault discovery, switching, and CLI-based note operations.

Community
Advanced
refactory-langrefactory-lang

speckit-bugfix

Creates a new branch and generates bug report for spec-kit projects.

Official
Intermediate