Agent Plugins Marketplace
← All plugins

issues

v1.0.0

Per-issue bug/feature/incident tracker that lives in docs/issues/ — one file per ticket with symptom, repro, root cause, fix, and verification. Includes a branch-on-start workflow and a hard rule to align with the user before implementing.

CodexClaude Code3 Skills

By mikersays0 GitHub starsUpdated 4 days ago

Directory evidence

Runtimes
Codex and Claude Code
Parsed components
3 skill or MCP entries
Source updated
Sep 19, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install issues for Codex and Claude Code

Installs for the current user
codex plugin marketplace add mikersays/mikersays-plugins
codex plugin marketplace upgrade mikersays-plugins
codex plugin add issues@mikersays-plugins

Paste and run these commands in a terminal with Codex. They add and refresh the mikersays-plugins catalog, then install this plugin.

Compatibility: the page URL and API slug “issues” remain stable.

  • Codex: issues@agent-plugin-marketplace → issues@mikersays-plugins

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/mikersays/mikersays-plugins

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/issues/.

Plugin files

plugins/issues/
├── .codex-plugin/plugin.json
├── .claude-plugin/plugin.json
├── skills/issue-close/SKILL.md
├── skills/issue-init/SKILL.md
└── skills/issue-new/SKILL.md

Included Skills3

issue-closeskills/issue-close/SKILL.md

Mark a docs/issues/ ticket as fixed after the change has shipped. Trigger when the user says "close ticket NNNN", "mark NNNN fixed", "ship issue 0010", "the invoicing bug is done", or after a successful merge of an issue branch. Stamps the merge commit SHA, requires a filled Verification section, and moves the INDEX.md line to Done. Diagnosis-preserving cousin of /plan-close.

issue-initskills/issue-init/SKILL.md

Bootstrap a docs/issues/ folder in the current repo for tracking bugs, features, and incidents as one markdown file per issue. Use whenever the user wants to set up issue tracking inside a repo, asks for a "ticket folder" / "bug tracker folder" / "docs/issues directory", or before they file the first ticket. /issue-new auto-inits if missing, so /issue-init is primarily for explicit setup or for refreshing the seed README/INDEX. Cousin of /plan-init — pick this when issues need a full diagnosis record and a branch-on-start workflow.

issue-newskills/issue-new/SKILL.md

File a new ticket under docs/issues/ for a bug, feature request, incident, or open question that should be tracked but isn't being fixed right now. Trigger whenever the user says "log this as a bug", "open a ticket for X", "track this issue", "create an issue for Y", "we should remember to fix Z", or describes something worth filing — even when they don't explicitly say "ticket". Reach for this skill instead of /plan-add when the issue needs a real diagnosis record (symptom, repro, root cause, fix, verification) rather than a quick todo line.

Plugin manifests2

plugins/issues/.codex-plugin/plugin.json
{
  "name": "issues",
  "description": "Per-issue bug/feature/incident tracker that lives in docs/issues/ — one file per ticket with symptom, repro, root cause, fix, and verification. Includes a branch-on-start workflow and a hard rule to align with the user before implementing.",
  "version": "1.0.0",
  "skills": "./skills/",
  "interface": {
    "displayName": "Issues",
    "shortDescription": "Per-issue bug and feature tracker with branch-on-start",
    "category": "Productivity"
  }
}
plugins/issues/.claude-plugin/plugin.json
{
  "name": "issues",
  "description": "Per-issue bug/feature/incident tracker that lives in docs/issues/ — one file per ticket with symptom, repro, root cause, fix, and verification. Includes a branch-on-start workflow and a hard rule to align with the user before implementing.",
  "version": "1.0.0",
  "author": {
    "name": "mikersays"
  }
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[issues on Agent Plugins Marketplace](https://pluginsmp.com/plugins/issues)