find-bugs

Identify charm bugs in newly written charm code before BUILD completion.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/tonyandrewmeyer/cantrip --skill find-bugs-tonyandrewmeyer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-bugs
Source: https://github.com/tonyandrewmeyer/cantrip/tree/main/src/cantrip/skills/find-bugs
Command: npx skills add https://github.com/tonyandrewmeyer/cantrip --skill find-bugs-tonyandrewmeyer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review newly written charm code for common charm bugs before finishing a BUILD task.

Core Features & Use Cases

  • Provides a structured checklist for status handling, event observation, and relation data checks.
  • Helps ensure charm quality before BUILD completion.
  • Use case: run this review alongside charm development tasks to detect and remediate issues before deployment.

Quick Start

Run a bug-hunting pass over the modified charm files and report HIGH priority issues first.

Frequently Asked Questions about find-bugs

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

FAQPage Schema
How do I catch charm bugs before finishing a BUILD task?

To catch charm bugs before BUILD completion, run a structured code review focusing on status handling, event observation, and Pebble layer interactions to identify and remediate issues early.

What common charm bugs should I look for during charm development?

Common charm bugs involve improper status handling, missed event observations, relation data check failures, and incorrect Pebble layer interactions. A structured checklist review helps detect these issues before deployment.

How does a structured code review help remediate Juju charm code issues?

A structured charm code review applies a multi-check process using a severity scale to prioritize found bugs. This provides clear remediation guidance, enabling you to fix HIGH priority issues first before BUILD completion.

When do I need to validate Pebble layer interactions in charm code?

Validate Pebble layer interactions during charm development when writing new code. Checking these interactions before BUILD completion ensures charm quality and prevents common deployment bugs related to service management.

Does this bug review process work for newly written charm code only?

The bug review process targets newly written charm code specifically. It runs a bug-hunting pass over modified charm files to ensure new changes pass status, event, and relation data checks before the BUILD finishes.