feedback-to-issues

Triage bootcamp feedback files into deduplicated GitHub issues with live MCP server re-verification.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin-development --skill feedback-to-issues-docktermj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feedback-to-issues
Source: https://github.com/docktermj/senzing-bootcamp-claude-plugin-development/tree/main/.claude/skills/feedback-to-issues
Command: npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin-development --skill feedback-to-issues-docktermj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of the Senzing Bootcamp plugin receive raw feedback files from bootcampers and must manually turn each entry into actionable, deduplicated GitHub issues while confirming every Senzing fact still holds against the live MCP server. ## Core Features & Use Cases - Per-entry duplicate detection: A bundled Python ledger script content-addresses each feedback entry (sha256 of normalized text) so overlapping feedback files are never re-processed. - Live fact re-verification: Every Senzing claim is re-checked against the current MCP server before filing, catching defects already fixed upstream or guidance the server now contradicts. - Structured issue filing: Generates GitHub issues from a strict template with root cause, acceptance criteria, provenance, and invariant references, plus optional upstream defect reports via submit_feedback. - Use Case: A maintainer drops SENZING_BOOTCAMP_PLUGIN_FEEDBACK.md into the repo and asks to process it; the skill classifies entries, skips known ones, files new issues, archives the file, and reports a triage table. ## Quick Start Process the feedback file SENZING_BOOTCAMP_PLUGIN_FEEDBACK.md at the repo root and file GitHub issues for any new entries.

Frequently Asked Questions about feedback-to-issues

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

FAQPage Schema
How do I turn user feedback files into GitHub issues automatically?▼

Place the feedback file at the repo root and invoke the skill; it parses each entry, checks a content-addressed ledger for duplicates, verifies Senzing facts against the live MCP server, and files one GitHub issue per actionable item after your approval.

How does the skill avoid filing duplicate issues from overlapping feedback files?▼

Each feedback entry is hashed (sha256 of normalized text) and recorded in feedback/PROCESSED.jsonl. The bundled feedback_ledger.py check command classifies files as NEW, PARTIAL, or DUPLICATE, and only new entries are triaged; open and closed GitHub issues are also searched before filing.

Does the skill verify feedback claims before creating issues?▼

Yes. Every Senzing-related claim is re-asked against the live MCP server using the tool that owns the fact, with the server version and date recorded in the issue. Claims the server cannot reach are marked observation-only, and unreachable servers produce unverified flags rather than guesses.

Can this skill modify plugin code or write into the specs directory?▼

No. It only creates GitHub issues, appends to the feedback ledger, and archives processed files under feedback/. The specs/ directory is a read-only archive, and implementing fixes is explicitly a separate later step.

What happens when a reported defect is actually the Senzing server's fault?▼

The skill drafts an anonymized technical bug report and, only after explicit maintainer approval, sends it upstream via submit_feedback. A plugin issue may still be filed to record the confirmed behavior, and the outcome is logged in the triage report.