skills.rest
opmau
opmauCOMMUNITY
Explore all skills by this author →
GitHub

document-bug

Create a Linear issue labeled bug with structured diagnostic details.

6|Updated Feb 7, 2026
Search Tags:#refactoring#evidence#linear#root-cause#document#issue-tracking#bug
One-click install
npx skills add https://github.com/opmau/claude-code-framework --skill document-bug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: document-bug
Source: https://github.com/opmau/claude-code-framework/tree/main/templates/.claude/skills/document-bug
Command: npx skills add https://github.com/opmau/claude-code-framework --skill document-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documenting a bug without modifying any source code, by creating a Linear issue labeled bug, helps teams track issues discovered during refactoring or maintenance without introducing changes to the codebase.

Core Features & Use Cases

  • Create a Linear issue with labels bug and discovered-in-session, keeping source files intact.
  • Capture structured details like Symptom, Evidence, Suspected Root Cause, Affected Module, and Fix Approach for later resolution.
  • Enforce a strict 'document, don't fix' workflow to avoid accidental code changes during investigation.

Quick Start

Invoke the /document-bug command with a brief symptom description to create a Linear issue.

Frequently Asked Questions about document-bug

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

FAQPage Schema
How do I document a bug in Linear without modifying source code?▼

You can document a bug without modifying source code by using a strict 'document, don't fix' workflow that creates a Linear issue labeled bug to keep source files intact during investigation.

What structured details do I need to log a Linear issue for a discovered bug?▼

To log a Linear issue for a discovered bug, you need to collect structured details including Symptom, Evidence, Suspected Root Cause, Affected Module, and Fix Approach for later resolution.

Can I track bugs found during code refactoring without altering the codebase?▼

Yes, you can track bugs found during code refactoring by creating a Linear issue labeled discovered-in-session, which enforces a strict workflow to avoid accidental code changes while investigating.

Do I need the Linear CLI to create traceable bug reports across sessions?▼

Yes, you need the Linear CLI installed to create traceable bug reports across sessions, as it guides the collection of evidence and suspected root cause before logging the issue.

Why document a suspected root cause instead of fixing the bug immediately?▼

Documenting a suspected root cause instead of fixing the bug immediately helps teams track issues discovered during maintenance without introducing accidental changes to the codebase during the investigation.

When should I use a document-only workflow for issue tracking during migrations?▼

You should use a document-only workflow for issue tracking during migrations or refactoring to enable traceable documentation across sessions while keeping source files strictly intact.

Related Skills

Explore More Software Engineering Skills→
georgekhananaevgeorgekhananaev
27

github-cli

Wrap GitHub CLI commands with risk classification and confirmation prompts.

Community
Intermediate
CidLucasCidLucas

triage-issue

Explore codebase root causes and create GitHub issues with TDD fix plans.

Community
Intermediate
SandroBeatzSandroBeatz

lint-check

Run ESLint and TypeScript type checking on a codebase.

Community
Intermediate
awinogradovawinogradov
5

linear:create

Create Linear issues with structured templates and wizard-based selections.

Community
Intermediate