report-feedback

Prepares privacy-scoped bug reports and feature requests for GitHub and Claude Code feedback.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/sergeiwallace/skills --skill report-feedback-sergeiwallace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-feedback
Source: https://github.com/sergeiwallace/skills/tree/main/skills/report-feedback
Command: npx skills add https://github.com/sergeiwallace/skills --skill report-feedback-sergeiwallace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires typer, skill-cli-foundation, and includes scripts (resource) components.

What problem does it solve? Writing a good bug report or feature request is tedious, and posting one publicly risks leaking session IDs, account identifiers, or other private diagnostics. This Skill drafts both a redacted public GitHub report and a private /feedback block from structured templates, and enforces a human confirmation gate before any GitHub write. ## Core Features & Use Cases - Template-driven drafting: Classifies the request as a bug or feature request and renders it from bundled Markdown templates with required product and OS version fields. - Privacy redaction: Strips session IDs, account/org identifiers, and private telemetry from the public draft while retaining them only in the private /feedback block. - Gated GitHub delivery: The default route returns a copy-paste /feedback block; the opt-in --via claude route may run gh issue create or gh issue comment only after the human confirms the exact repository, title, and body. - Use Case: After Claude Code crashes, ask the Skill to prepare a bug report; it searches for existing issues, drafts a redacted public report and a private feedback block, and waits for your approval before posting anything. ## Quick Start Ask the assistant to prepare a bug report about the problem you just hit, for example by saying "report a bug where the CLI hangs on startup" and then review the rendered drafts.

Frequently Asked Questions about report-feedback

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

FAQPage Schema
How do I write a bug report for GitHub without leaking private information?

Classify the issue as a bug, render it from the bundled bug template, and run the redaction check before delivery. The public draft strips session IDs, account identifiers, and telemetry, which are kept only in the private /feedback block.

How do I submit feedback to Claude Code from a session?

The Skill renders a ready-to-copy /feedback block containing private diagnostic context such as session ID and OS details. You paste it manually into the interactive /feedback command; the Skill never invokes that command itself.

Can this Skill create a GitHub issue automatically?

Only via the explicit opt-in `--via claude` route. Even then, it shows the exact repository, title, rendered body, and redaction result, and runs `gh issue create` or `gh issue comment` only after you confirm.

What is the difference between the feedback and claude routes?

The default feedback route only returns drafts for manual pasting and never writes to GitHub. The claude route permits a direct GitHub write after human confirmation, while still returning the /feedback block for optional manual submission.

What dependencies does the report-feedback route resolver need?

The resolver script runs with uv and requires Python 3.11+, the typer package, and the bundled skill-cli-foundation package. The GitHub CLI (gh) is needed only for the opt-in claude delivery route.