report-bug

Capture bug details locally, deduplicate by fingerprint, and create GitHub issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hodor/claude-compass --skill report-bug-hodor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-bug
Source: https://github.com/hodor/claude-compass/tree/main/plugin/skills/report-bug
Command: npx skills add https://github.com/hodor/claude-compass --skill report-bug-hodor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, github-cli, and includes scripts (resource) components.

What problem does it solve?

The report-bug Skill streamlines the process of reporting bugs in the Compass project, reducing time and ensuring that issues are correctly documented and handled.

Core Features & Use Cases

  • Bug Reporting: Automatically captures detailed bug information and reports it to the Compass GitHub repository.
  • Duplicate Check: Ensures that reported bugs are unique to avoid redundant issue tracking.
  • CLI Integration: Integrates with the Compass command-line interface for efficient bug capture and filing.

Quick Start

Run 'compass report-bug "Bug description"' to report a bug in Compass.

Frequently Asked Questions about report-bug

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

FAQPage Schema
How do I report a bug in the Compass project?

To report a Compass bug, run 'compass report-bug "Bug description"' in your CLI. The Skill captures local details, deduplicates entries by fingerprint, and creates a GitHub issue if no duplicates are found.

Does reporting Compass bugs automatically check for duplicate issues on GitHub?

Yes, the bug reporting process includes a duplicate check that fingerprints each entry. It searches existing GitHub issues before creating a new one to avoid redundant issue tracking in the Compass repository.

Do I need a GitHub account to file Compass bug reports from the command line?

Yes, you need a GitHub account and the github-cli dependency installed to file issues. The bug reporting Skill requires Bash and authenticated GitHub CLI access to create issues in the Compass repository.

What's the best way to track and document operational errors in Compass?

The best way to track Compass operational errors is using the report-bug CLI command, which automatically captures detailed bug information locally and documents it directly to the Compass GitHub repository.

Why does my Compass bug report skip creating a new GitHub issue?

Your Compass bug report skips GitHub issue creation when the duplicate check finds an existing entry matching your bug's fingerprint. This prevents redundant issue tracking in the Compass repository.