Skill

report-issue

Use when the user says "plugin-dev got this wrong", "plugin-dev is missing X", "report an issue with plugin-dev", "plugin-dev told me the wrong thing", or invokes /plugin-dev-sync:report-issue. Provides guided feedback collection and triggers automatic root-cause analysis, patching, and PR creation.

Install

npx claudepluginhub karimstekelenburg/k3m-marketplace --plugin plugin-dev-sync

Tool Access

This skill is limited to using the following tools:

ReadWriteEditBashGlobGrepAgentWebFetch

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.6k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.6k

Command Development

10 files

Guides slash command development for Claude Code: structure, YAML frontmatter, dynamic arguments, bash execution, user interactions, organization, and best practices.

plugin-dev

83.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 29, 2026

Actions

View Source View Plugin View on GitHub View README

Report Issue

Collect structured feedback about plugin-dev failures and trigger an automated fix pipeline that patches both plugin-dev and plugin-dev-sync if needed.

Feedback Collection

If $ARGUMENTS is provided, use it as the initial issue description. Otherwise, gather the following from the user's report:

What happened: What did plugin-dev do wrong or miss?
What was expected: What should it have done instead?
Context: Which skill/agent/command was involved?
Evidence (optional): Links, docs, or examples proving the correct behavior

If the user's initial report is vague, ask one focused clarifying question. Do not ask more than one follow-up.

Structured Issue Format

Compile the feedback into a structured issue:

## Issue Report

- **Reporter**: user
- **Date**: YYYY-MM-DD
- **Component**: skill/agent name
- **Symptom**: what went wrong
- **Expected**: what should have happened
- **Evidence**: links or references

Automated Fix Pipeline

After collecting the issue, launch the issue-analyst agent with the structured issue. The agent will:

Diagnose: Identify the root cause in plugin-dev (wrong info in a skill, missing reference, outdated example, weak trigger description, etc.)
Verify: Cross-reference against official sources to confirm the correct information. Fetch relevant docs if needed.
Patch plugin-dev: Apply the fix to the appropriate files
Validate: Run claude plugin validate on plugin-dev
Check plugin-dev-sync: Determine if the bug was introduced by a previous plugin-dev-sync sync (check git blame). If so, identify what went wrong in plugin-dev-sync's discovery/review pipeline and patch it too.
Commit and PR: Create a branch, commit changes, and open a PR with:
- The original issue report
- Root cause analysis
- What was fixed and where
- Whether plugin-dev-sync was also patched and why
- Validation results

PR Branch Naming

plugin-dev-sync/fix-<component>-<short-description>

Example: plugin-dev-sync/fix-hook-dev-missing-stop-event

When Meta-Dev Itself Needs Fixing

If the issue-analyst determines plugin-dev-sync's pipeline caused the problem (e.g., the discovery-crawler missed a feature, or the diff-reviewer approved a bad change), it should:

Identify which plugin-dev-sync component failed
Patch the relevant agent prompt or skill instructions
Include both plugin-dev and plugin-dev-sync changes in the same PR
Explain the plugin-dev-sync fix in the PR report

</description>