filament-bug-report-format

Generate anonymized Filament bug reports with sanitized database snapshots.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates an anonymized bug-report directory containing a sanitized database snapshot, environment details, and structured reproduction steps to help teams reproduce issues without exposing sensitive data.

Core Features & Use Cases

  • Gather bug context from users (symptoms, expected behavior, steps to reproduce).
  • Capture environment and project state, then anonymize sensitive content in the local Filament database.
  • Export anonymized state as JSON and attach it to a bug report, plus a ready-to-fill BUG-REPORT.md.
  • Optional: collect recent CLI history to aid debugging.

Quick Start

Run the bug-report workflow to generate an anonymized snapshot of your local Filament state and a ready-to-attach bug report.

Frequently Asked Questions about filament-bug-report-format

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

FAQPage Schema
How do I create an anonymized bug report from my local Filament state?

Yes, the bug report workflow sanitizes sensitive content in your local Filament database (.fl/fl.db) by generating an anonymized state exported as JSON, ensuring safe sharing without exposing sensitive data.

What files and artifacts are included in a Filament bug report package?

A Filament bug report package includes an anonymized database snapshot exported as JSON, captured environment details, a BUG-REPORT.md file, and optionally collected recent CLI history to aid debugging.

Do I need a specific database setup to generate an anonymized Filament bug report?

You need a local Filament setup with access to the project database at .fl/fl.db. The workflow captures the environment and project state, anonymizes sensitive content, and exports the sanitized snapshot for the bug report.

Can I collect CLI history to help reproduce database bugs in Filament?

Yes, the bug report workflow optionally collects recent CLI history to aid debugging. This history is gathered alongside the anonymized database snapshot and environment details to help teams reproduce issues.

What is the best way to share local Filament debugging context safely with a team?

The best way to share Filament debugging context safely is to generate a sanitized bug report directory containing an anonymized database snapshot and environment details, enabling safe sharing without exposing sensitive data.