Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub ivintik/private-claude-marketplace --plugin plugin-opsHow this skill is triggered — by the user, by Claude, or both
Slash command
/plugin-ops:issuesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
---
Tracks project blockers, bugs, and gaps across sessions with persistent issue storage. Lists, adds, and resolves issues with categories and severity.
Manages full GitHub issue lifecycle: create with conventional commit titles, sub-issues, cross-repo links, edit/view/list, dump trees to markdown/YAML, push from files, comment/label/close.
Creates GitHub issues in WaterplanAI/agentic-config repo for bugs and feature requests using GitHub CLI. Handles templates, explicit args, or extracts from conversation context. Invoke via /ac-issue.
Share bugs, ideas, or general feedback.
Manage the structured ISSUES.md file for any Claude Code plugin.
Parse $ARGUMENTS:
--init: Create a new ISSUES.md--add: Add a new issue (prompts for details)--resolve ISSUE-NNN: Mark as resolved--update ISSUE-NNN: Update an existing issue--list: List all issues (default if no flag)Cache guard: ~/.claude/plugins/cache/ is READ-ONLY. Resolve to the real git repo via atlas: atlas_search_projects(query="plugin-name").
Skip if exists. Create at plugin root:
# Plugin Issues
<!-- Managed by /plugin-ops:issues — see knowledge/lifecycle-formats.md for format -->
No issues tracked yet.
Read ISSUES.md, display summary:
Plugin: {name} — {count} issues ({open} open, {resolved} resolved)
| ID | Status | Severity | Title |
|----|--------|----------|-------|
Extract from context first — only prompt for missing fields. The user often provides details inline (e.g. "log issue: X should not require Y"). Check conversation context for:
If all 4 are clear from context, write directly — no prompts needed. Auto-create ISSUES.md if missing.
Format from knowledge/lifecycle-formats.md:
## ISSUE-{NNN}: {Title}
- **Status**: open
- **Severity**: {severity}
- **Found**: {today YYYY-MM-DD}
- **Resolved**: —
- **Context**: {context}
- **Description**: {description}
- **Resolution**: —
- **Notes**:
Find issue, update: status → resolved, set resolved date, set resolution description (ask user).
Find issue, ask what to update: status, notes, severity, or description. Apply with Edit tool.
--init/--add: suggest --init