bug

Inserts a bug report into the TurkeysCRM's bug_reports table via Supabase MCP.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/panlam85/PAF-Atlas --skill bug-panlam85
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug
Source: https://github.com/panlam85/PAF-Atlas/tree/main/.claude/skills/bug
Command: npx skills add https://github.com/panlam85/PAF-Atlas --skill bug-panlam85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

File a bug report into TheaterCRM's bug_reports table via Supabase MCP.

Core Features & Use Cases

  • Pure note-taking: captures the user's bug text after /bug and inserts a row with preset identifiers; does not modify code or dev server.
  • Deterministic: always performs a single insert with fixed fields; returns ID and summary.

Quick Start

Tell me a bug description after /bug to file a new bug report.

Frequently Asked Questions about bug

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

FAQPage Schema
How do I log a bug report into TheaterCRM?

To log a bug report into TheaterCRM, trigger the /bug command and provide the raw text description. The system inserts a single row into the bug_reports table via Supabase MCP using preset project and reporter identifiers, returning the new ID and summary.

Does the bug logging skill modify code or attempt automated fixes?

No, the bug logging skill does not modify code or attempt automated fixes. It functions purely as a note-taking tool, capturing your text after the /bug trigger to perform a deterministic database insert into the bug_reports table without touching the dev server.

Can I use Supabase MCP to insert issue-tracking records with preset identifiers?

Yes, you can use Supabase MCP to insert issue-tracking records. This skill performs a single INSERT operation into the bug_reports table using preset identifiers for the project, reporter, and organization, ensuring a deterministic logging process.

What do I need to file a bug report using Supabase MCP?

To file a bug report using Supabase MCP, you need a configured environment with preset identifiers for your project, reporter, and organization. You simply provide the raw bug text after the /bug trigger, and the system handles the database insertion.

Are there limitations to the data captured during issue-tracking with TheaterCRM?

Yes, a limitation is that the issue-tracking insert uses fixed fields and a preset environment. It captures the raw user text deterministically and always performs a single insert, meaning dynamic project switching or custom field mapping is not supported.