Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills Aโ€“Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

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
0 views
Added 9/20/2026
ai-agentsbash

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$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 automatically 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.

Download Zip
Files
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

tstaplertstapler
View sourceMore from tstapler โ†’
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots ยท $299/mo ยท GSC-verified traffic ยท sponsors can never buy grades.

See placements

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots ยท $299/mo ยท GSC-verified traffic ยท sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

1023331 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3331 votes

catchup

Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.

611 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants โ€” handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents โ†’