bugs

Document known bugs, quirks, and workarounds for ikigai dependencies and tooling.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/mgreenly/ikigai --skill bugs-mgreenly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugs
Source: https://github.com/mgreenly/ikigai/tree/main/.claude/library/bugs
Command: npx skills add https://github.com/mgreenly/ikigai --skill bugs-mgreenly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Known bugs and quirks in dependencies and tools documented for ikigai.

Core Features & Use Cases

  • Centralized catalog of issues, evidence, and workarounds for dependencies and tooling.
  • Quick-reference troubleshooting for environmental discrepancies (e.g., lcov version reporting).
  • Use Case: when a tool behaves unexpectedly, consult these notes to apply the documented workaround.

Quick Start

Review the lcov version reporting bug and follow the documented workaround to confirm the actual version.

Frequently Asked Questions about bugs

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

FAQPage Schema
How do I fix lcov version reporting anomalies on Debian-based systems?

To fix lcov version reporting anomalies on Debian-based systems, consult the centralized bug catalog to apply the documented workaround and confirm the actual installed version.

How do I troubleshoot dependency packaging discrepancies in my environment?

Troubleshoot dependency packaging discrepancies by referencing the documented issues and evidence catalog, then applying the recommended diagnostic steps and remediation actions for environmental mismatches.

What is the best way to document known tool bugs and workarounds for a project?

The best way to document known tool bugs and workarounds is to maintain a centralized catalog of issues, evidence, and remediation steps that encodes observations as actionable guidance for quick reference.

Does this bug catalog cover environment mismatches across Debian-based systems?

Yes, the bug catalog covers environment mismatches across Debian-based systems, providing quick-reference troubleshooting and documented workarounds for tool and dependency quirks encountered in real-world scenarios.

Why does a dependency tool behave unexpectedly during version reporting?

A dependency tool behaves unexpectedly during version reporting due to known bugs and quirks documented in the catalog, which provides diagnostic steps to identify the issue and recommended remediation to resolve it.

What should I do when a tool behaves unexpectedly and I need a documented workaround?

When a tool behaves unexpectedly, consult the notes in the bug catalog to apply the documented workaround, following the diagnostic steps and recommended remediation to resolve the specific tool quirk.