← ClaudeAtlas

report-feedbacklisted

Prepare privacy-scoped bug reports or feature requests for public GitHub and authenticated Claude Code feedback, with an explicit human gate before any GitHub write.
sergeiwallace/skills · ★ 0 · Data & Documents · score 73
Install: claude install-skill sergeiwallace/skills
# report-feedback Prepare reports; do not freehand them. This skill is self-contained: classify the request, then read the matching bundled template before drafting: - [bug template](templates/bug.md) - [feature-request template](templates/feature-request.md) **Usage:** `/report-feedback [--via feedback|claude] <bug description | feature request | issue reference | affected product>` Before rendering, resolve the selected route: ```bash uv run --script "${CLAUDE_SKILL_DIR}/scripts/report_feedback_route.py" \ [--via feedback|claude] "<bug description | feature request | issue reference | affected product>" ``` `uv` runs the bundled resolver and `gh` is needed only for the opt-in `claude` route. The resolver uses the bundled `skill-cli-foundation` package. `--via` defaults to `feedback`; its enum validation rejects any other route before rendering starts. ## Drafting process 1. Classify the report as a bug or feature request, select its bundled template, and search the intended public repository (when known) for an existing matching issue or discussion before drafting a new report. Refine or comment on an existing report when that is the appropriate outcome; do not create a duplicate. 2. If the project has its own tracking location, search it for a matching report and refine that record in place. Otherwise, ask the human to name a local record file, or keep the draft in the response until they choose one. Do not assume a particular project directory exi