bug-report-format

Create anonymized bug report directories with database snapshots and reproduction steps.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/JYC11/filament --skill bug-report-format-jyc11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-report-format
Source: https://github.com/JYC11/filament/tree/main/.claude/skills/bug-report-format
Command: npx skills add https://github.com/JYC11/filament --skill bug-report-format-jyc11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Anonymizing local project state is essential for sharing bug reports without exposing sensitive data. This skill creates a self-contained bug-report directory that includes an anonymized database snapshot, an environment capture, and a structured reproduction steps template.

Core Features & Use Cases

  • Anonymized environment capture
  • Self-contained bug report directory with anonymized DB snapshot and JSON export
  • Reproduction steps template with guidance and attachments
  • Optional capture of recent CLI history to provide context
  • Guidance for reviewers on what to inspect without exposing secrets

Quick Start

Fill in the bug details and run the workflow to generate a ready-to-share bug report directory.

Frequently Asked Questions about bug-report-format

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

FAQPage Schema
How do I anonymize local project state for a bug report?

To anonymize local project state for a bug report, this skill generates a self-contained directory featuring an anonymized database snapshot and environment capture, preserving schema and relations while removing sensitive user data.

What is the best way to share reproduction steps without exposing secrets?

The best way to share reproduction steps without exposing secrets is using a structured template that guides you through capturing the environment and anonymizing data, ensuring reviewers can inspect the issue safely.

Can I export an anonymized database snapshot as a JSON file?

Yes, you can export an anonymized database snapshot as a JSON file. The skill creates a self-contained bug report directory that includes a JSON export of your local state with sensitive user data removed.

Does this bug report workflow capture recent CLI history?

Yes, this bug report workflow optionally captures recent CLI history. This provides additional context for reviewers to understand the sequence of commands leading to the issue within the anonymized bug report directory.

What is included in a self-contained bug report directory?

A self-contained bug report directory includes an anonymized database snapshot, an environment capture, and a structured reproduction steps template with guidance and attachments for reviewers.

When do I need an anonymized environment capture for bug reporting?

You need an anonymized environment capture for bug reporting when sharing local project state externally. It allows you to reproduce the issue for reviewers while ensuring sensitive user data and secrets are stripped out.