Skip to content
Back to skills

Log Bug

ASecurity

Quickly document a new bug into docs/bugs/open/ using the project-coordinator format

  • 8 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 20, 2026
ai-agentsbash

Security analysis

A100/100

Scanned September 20, 2026

npx -y skills add tstapler/dotfiles --skill log-bug --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Log Bug?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Log Bug
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/tstapler-log-bug/badge)](https://www.skillsdirectory.com/skills/tstapler-log-bug)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: Quickly document a new bug into docs/bugs/open/ using the project-coordinator format
---

# Log Bug

Quickly capture and document a new bug into `docs/bugs/open/` following the project-coordinator bug tracking format.

## Bug

${1:-Describe the bug}

## Instructions to Claude

**Step 1: Gather bug details**

If `{{args}}` provides enough context, proceed. Otherwise ask for:
- What happened vs. what was expected?
- How to reproduce it (steps if known)
- Severity assessment: Critical / High / Medium / Low
  - **Critical**: Blocks core functionality, data loss risk
  - **High**: Major feature broken, significant impact
  - **Medium**: Noticeable issue, workaround exists
  - **Low**: Minor / cosmetic / edge case

**Step 2: Determine next BUG ID**

Scan `docs/bugs/` across all subdirectories to find the highest existing BUG-### number, then increment by 1.

```bash
find docs/bugs -name "BUG-*.md" | sort | tail -5
```

**Step 3: Create the bug file**

Create `docs/bugs/open/BUG-{###}-{kebab-case-title}.md` with this structure:

```markdown
# BUG-{###}: {Short Title} [SEVERITY: {Level}]

**Status**: πŸ› Open
**Discovered**: {today's date}
**Impact**: {what functionality is affected and who is impacted}

## Problem Description

{Clear description of what's wrong}

## Reproduction Steps

1. {Step 1}
2. {Step 2}
3. Expected: {what should happen}
4. Actual: {what actually happens}

## Root Cause

{Unknown β€” needs investigation / or analysis if known}

## Files Likely Affected

- {file path} β€” {why it's relevant}

## Fix Approach

{Unknown / or proposed approach if obvious}

## Verification

{How to confirm the bug is fixed}

## Related Tasks

{Links to any related docs/tasks/ files if applicable}
```

**Step 4: Surface the bug**

After creating the file, output a summary:
- Bug ID and title
- Severity and why
- Recommended priority relative to current work (check `docs/bugs/open/` for existing bugs)
- Whether this should interrupt current work or be queued

Execute this workflow now for: ${1:-Describe the bug}

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…