report-issue

Collects structured feedback on plugin-dev failures and triggers automated diagnosis, patching, and PR creation.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/karimStekelenburg/k3m-marketplace --skill report-issue-karimstekelenburg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: report-issue
Source: https://github.com/karimStekelenburg/k3m-marketplace/tree/main/plugins/plugin-dev-sync/skills/report-issue
Command: npx skills add https://github.com/karimStekelenburg/k3m-marketplace --skill report-issue-karimstekelenburg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When plugin-dev gives wrong or missing information, users need a way to report the issue and have it fixed automatically instead of manually debugging the plugin's skills, agents, and references. ## Core Features & Use Cases - Guided Feedback Collection: Gathers what happened, what was expected, which component was involved, and supporting evidence into a structured issue report. - Automated Fix Pipeline: Launches an issue-analyst agent that diagnoses the root cause, verifies against official sources, patches plugin-dev, and validates with claude plugin validate. - Self-Healing Meta-Pipeline: Checks via git blame whether plugin-dev-sync's sync pipeline introduced the bug and patches it in the same PR. - Use Case: A user notices plugin-dev's hook-dev skill is missing the Stop event. They invoke the skill with a short description, and it produces a branch like plugin-dev-sync/fix-hook-dev-missing-stop-event with a PR containing the root-cause analysis and fix. ## Quick Start Invoke the skill with a short description of what plugin-dev got wrong, for example by saying plugin-dev is missing the Stop hook event in hook-dev.

Frequently Asked Questions about report-issue

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

FAQPage Schema
How do I report an issue with a Claude Code plugin?▼

Invoke the report-issue skill with a short description of what went wrong, such as what plugin-dev did incorrectly or missed. The skill collects structured feedback and automatically triggers diagnosis, patching, and PR creation.

How to automatically fix wrong information in a Claude Code plugin?▼

The skill launches an issue-analyst agent that diagnoses the root cause, verifies correct behavior against official documentation, patches the affected files, and runs claude plugin validate before opening a PR.

What information should I include when reporting a plugin bug?▼

Provide what happened, what was expected, which skill or agent was involved, and optionally links or docs proving the correct behavior. If your report is vague, the skill asks at most one clarifying question.

Can the fix pipeline detect bugs introduced by automated syncs?▼

Yes, the issue-analyst checks git blame to determine whether a previous plugin-dev-sync sync introduced the bug. If so, it identifies the failing pipeline component and patches plugin-dev-sync in the same PR.

What happens after the issue is diagnosed and patched?▼

The agent creates a branch named plugin-dev-sync/fix-<component>-<description>, commits the changes, and opens a PR containing the original issue report, root-cause analysis, fixes applied, and validation results.