file-bug-insight

File Insight product defects as triaged GitHub issues with reproduction evidence.

10|9|Updated May 22, 2026
One-click install
npx skills add https://github.com/constructorfabric/insight --skill file-bug-insight-constructorfabric
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-bug-insight
Source: https://github.com/constructorfabric/insight/tree/main/.claude/skills/file-bug-insight
Command: npx skills add https://github.com/constructorfabric/insight --skill file-bug-insight-constructorfabric

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Filing a useful bug report is hard: duplicates get created, evidence is missing, internal details leak into a public repo, and speculative root causes mislead the assignee. This Skill turns an observed Insight product defect into a complete, scrubbed GitHub issue in constructorfabric/insight that a reader can act on in under a minute. ## Core Features & Use Cases - Duplicate triage: Searches open and closed issues separately before filing, comments on existing issues instead of duplicating, and flags closed matches as regressions. - Evidence-driven reporting: Walks the bronze/silver/gold medallion layers in ClickHouse for data bugs, captures browser console and API responses for UI bugs, and records version plus reproduction rate in every report. - Public-repo hygiene: Scrubs internal hostnames, tokens, and personal data from the body, confirms the draft with you, then creates the issue with native Bug type, adds it to the Insight project board, and sets the Priority field. - Use Case: After reproducing a metric that shows no data, run the three-layer ClickHouse check, confirm bronze has rows but gold does not, and file a scrubbed issue with the query outputs attached. ## Quick Start Ask the assistant to file an Insight bug for the defect you just reproduced, providing the symptom and any evidence you collected.

Frequently Asked Questions about file-bug-insight

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

FAQPage Schema
How do I file a bug report as a GitHub issue with gh CLI?

Search open and closed issues separately with gh issue list to avoid duplicates, write the body to a file outside the repo, then run gh issue create with --type Bug and --body-file. Add the issue to the project board with gh project item-add and set the priority field with gh project item-edit.

What evidence should a data or metric bug report include?

Run the same query at the bronze, silver, and gold ClickHouse layers and record all three results, including the ones that look normal. Also include the version reproduced on and the reproduction rate as attempts out of total, such as 10/10 for deterministic failures.

Should a bug report include root cause analysis?

No. This Skill enforces observations-only reports: paste what you ran and what it returned, but leave diagnosis to the assignee. A confident wrong cause in the body sends the assignee down the wrong path before they start.

How do I avoid filing duplicate GitHub issues?

Search open and closed states in two separate queries, since closed issues rank after open ones in a combined search and fall off the result window. Search multiple times with different vocabulary like the metric key, error code, and user-visible label.

What must be scrubbed from issues in a public repository?

Remove internal hostnames, cluster and kube context names, workspace paths, JWTs, tokens, credentials, and exact data values tied to real people. Keep the product's own code references such as file paths, table names, and API routes, since those make the bug actionable.

When is a failure an environment problem instead of a product bug?

A metric that is empty because nothing was seeded or synced is not a product defect. Check the bronze layer first: if there are no raw rows for that connector and window, it is a seed or sync gap and no issue should be filed.