bugcheck

Search repository documentation, comments, and commit messages for past bug investigations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jpratt9/dotfiles --skill bugcheck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugcheck
Source: https://github.com/jpratt9/dotfiles/tree/main/.agents/skills/bugcheck
Command: npx skills add https://github.com/jpratt9/dotfiles --skill bugcheck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill assists in quickly identifying existing bug investigations, post-mortems, and documented issues within a repository, saving developers time and reducing debugging cycles.

Core Features & Use Cases

  • Bug and Issue Identification: Search current repository for prior occurrences of bugs or issues.
  • Document and Code Analysis: Scan documentation, code comments, and commit messages for matches.
  • Use Case: If you encounter a specific error or bug in your project, use this Skill to quickly find any related past issues and understand potential fixes.

Quick Start

Use the bugcheck skill to search for issues related to 'database connectivity error' in this repository.

Frequently Asked Questions about bugcheck

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

FAQPage Schema
How do I find past bug investigations and post-mortems in a repository?

To find past bug investigations and post-mortems in a repository, search documentation, code comments, and commit messages. This skill scans markdown, text, rst, adoc, pdf, and org files to locate documented issues.

Can I search git commit messages and test files for previous issue resolutions?

Yes, you can search git commit messages and test files for previous issue resolutions. The tool performs text search across commit history and test files to identify past bug fixes and related investigations.

What is the best way to analyze code comments for documented issues before debugging?

Analyzing code comments for documented issues before debugging involves scanning existing documentation and commit messages for matching text. This approach reveals prior occurrences of bugs to accelerate current error resolution.

Does this repository search tool support scanning PDF and AsciiDoc files for known bugs?

Yes, this repository search tool supports scanning PDF and AsciiDoc files for known bugs. It performs text search across pdf and adoc files, alongside markdown and text formats, to locate documented issues.

How to identify if a specific database connectivity error was previously resolved in my project?

To identify if a specific database connectivity error was previously resolved, use the skill to search repository documentation and commit messages for related keywords. It locates prior occurrences and post-mortems to enable efficient resolution.