skills.rest
cmtkdot
cmtkdotCOMMUNITY
Explore all skills by this author →
GitHub

bug

Analyze logs and stack traces to plan fixes for user-reported bugs.

Updated Aug 23, 2026
Search Tags:#debugging#investigation#code-analysis#bug#stack-trace#patch-planning
One-click install
npx skills add https://github.com/cmtkdot/arc --skill bug-cmtkdot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug
Source: https://github.com/cmtkdot/arc/tree/main/skills/bug
Command: npx skills add https://github.com/cmtkdot/arc --skill bug-cmtkdot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly identify, analyze, and plan fixes for user-reported bugs and failures by collecting relevant logs, traces, and contextual information.

Core Features & Use Cases

  • Bug triage and reproduction planning: gather logs, stack traces, and user reports to define a fix plan.
  • Open-spec guided fix planning: output fixes with concrete code changes and testing steps.
  • Safe, view-only workflow: ensure no state changes occur during investigation, preserving repository integrity.

Quick Start

Provide the bug details to arc and request a bug investigation and fix plan.

Frequently Asked Questions about bug

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

FAQPage Schema
How do I investigate a user-reported bug using logs and stack traces?▼

To investigate a bug, you analyze logs and stack traces to identify the root cause, then generate an open-spec fix plan with concrete code changes and testing steps for structured bug triage.

What is an open-spec fix plan for software crash reports?▼

An open-spec fix plan is a structured output that defines concrete code changes and testing steps required to resolve a crash, providing a clear execution path derived from analyzing logs and stack traces.

How do I plan fixes for software bugs without altering the repository state?▼

You can plan fixes without altering state by using a safe, view-only workflow during bug investigation, ensuring no changes occur while gathering logs and traces and generating the architectural fix plan.

Can I use this approach for crash report analysis across different software projects?▼

Yes, this bug triage approach applies to error reports and crash reports across various software projects, analyzing user feedback and stack traces to enable structured investigation and architectural fix planning.

What's the best way to structure bug triage and reproduction planning?▼

The best way to structure bug triage is to gather logs, stack traces, and user reports to define a concrete fix plan, using a background agent to collect context and present an actionable execution path.

Related Skills

Explore More Software Engineering Skills→
Ilenburg1993Ilenburg1993
3

reactive-bug-audit

Analyze stack traces and logs to identify root causes and apply minimal patches.

Community
Intermediate
shiaho777shiaho777
5.5k

debug

Diagnose and fix software bugs through a reproducible debugging workflow.

Community
Intermediate
s1366560s1366560
5

gitnexus-exploring

Index and analyze code repositories to trace execution flows and identify symbol dependencies.

Community
Intermediate
jellyrockjellyrock
37

runtime-triage

Classify Roku BrightScript crash logs and generate investigation handoff packets.

Official
Advanced