From feedback-plugin
Analyzes conversation for skill feedback and creates labeled GitHub issues for bugs, enhancements, and positive outcomes. Use when skills fail, suggest better patterns, or perform well.
npx claudepluginhub laurigates/claude-plugins --plugin feedback-pluginThis skill is limited to using the following tools:
Analyze the current session for skill feedback and create GitHub issues to track bugs, enhancements, and positive patterns.
Conducts multi-round deep research on GitHub repos via API and web searches, generating markdown reports with executive summaries, timelines, metrics, and Mermaid diagrams.
Dynamically discovers and combines enabled skills into cohesive, unexpected delightful experiences like interactive HTML or themed artifacts. Activates on 'surprise me', inspiration, or boredom cues.
Generates images from structured JSON prompts via Python script execution. Supports reference images and aspect ratios for characters, scenes, products, visuals.
Analyze the current session for skill feedback and create GitHub issues to track bugs, enhancements, and positive patterns.
| Use this skill when... | Use alternative when... |
|---|---|
| A skill gave wrong or outdated guidance | Want to update skills directly -> /project:distill |
| A command failed due to skill advice | Need static skill quality analysis -> /health:audit |
| Discovered a better flag or pattern | Want to capture general learnings -> /project:distill |
| A skill worked particularly well | Want to track command usage stats -> /analytics-report |
| End of session, want to file feedback | Need to fix a skill right now -> edit the SKILL.md directly |
git remote -vgh issue list --label session-feedback --state open --json number,title --jq '.[].title'gh issue list --label positive-feedback --state open --json number,title --jq '.[].title'Parse these from $ARGUMENTS:
| Parameter | Description |
|---|---|
--dry-run | Show findings without creating issues |
--bugs-only | Only report bugs (wrong/outdated guidance) |
--enhancements-only | Only report enhancement opportunities |
--positive-only | Only report positive feedback |
[plugin-name] | Scope analysis to a specific plugin |
Execute this session feedback workflow:
Check and create required labels:
session-feedback label exists: gh label list --json name --jq '.[].name' | grep -q session-feedbackgh label create session-feedback --description "Feedback from session analysis" --color "d876e3"positive-feedback label exists similarlygh label create positive-feedback --description "Skills that worked well" --color "0e8a16"Review the entire conversation for feedback signals. Look for these categories:
Bugs (label: session-feedback, bug):
Enhancements (label: session-feedback, enhancement):
Positive (label: positive-feedback):
For each finding, record:
Filter by $ARGUMENTS:
--bugs-only: only report bugs--enhancements-only: only report enhancements--positive-only: only report positive feedback[plugin-name] specified: only report for that pluginFor each finding, search for existing issues:
gh issue list --label session-feedback --search "<skill-name> <key-phrase>" --json number,title --jq '.[].title'
Skip findings that match an existing open issue title. Note skipped items for the summary.
Use AskUserQuestion to present categorized findings. Group by category:
Format each finding as:
[BUG] plugin-name/skill-name: brief description
[ENH] plugin-name/skill-name: brief description
[POS] plugin-name/skill-name: brief description
Let the user select which findings to file as issues (use multiSelect).
If --dry-run, present findings and stop here.
For each approved finding, create a GitHub issue:
Title format: feedback(<plugin-name>): <description>
Labels:
session-feedback, bugsession-feedback, enhancementpositive-feedbackBody template:
## Skill
`<plugin-name>/skills/<skill-name>/SKILL.md`
## Category
<Bug | Enhancement | Positive feedback>
## Description
<What happened during the session>
## Evidence
<Specific interaction, error message, or successful outcome>
## Suggested Action
<What should change in the skill, or what should be preserved>
Create each issue: gh issue create --title "feedback(<plugin>): <desc>" --label "<labels>" --body "<body>"
Print a summary:
| Metric | Count |
|---|---|
| Findings identified | N |
| Duplicates skipped | N |
| Issues created | N |
| Skipped by user | N |
List created issue numbers with links.
| Context | Command |
|---|---|
| List feedback issues | gh issue list --label session-feedback --json number,title,labels -q '.[]' |
| Search for duplicates | gh issue list --label session-feedback --search "keyword" --json title -q '.[].title' |
| Create label | gh label create name --description "desc" --color "hex" |
| Create issue | gh issue create --title "t" --label "l1,l2" --body "b" |
| Check label exists | gh label list --json name -q '.[].name' |
| Flag | Description |
|---|---|
--dry-run | Show findings without creating issues |
--bugs-only | Only bug reports |
--enhancements-only | Only enhancement suggestions |
--positive-only | Only positive feedback |
[plugin-name] | Scope to specific plugin |