skills.rest
Negentropy-Laby
Negentropy-LabyOFFICIAL
Explore all skills by this author →
GitHub

bug-report

Generate structured bug reports with reproduction steps, severity, and classification.

3|Updated Jun 3, 2026
Search Tags:#documentation#qa#code#triage#analyze#bug-report
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill bug-report-negentropy-laby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/bug-report
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill bug-report-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

bug-report solves the problem of converting informal bug descriptions or scattered code observations into consistent, auditable bug reports that include reproduction steps, severity, and context.

Core Features & Use Cases

  • Structured template: generates a complete bug report with the required fields.
  • Analyze mode: reads target files to surface potential bugs and suggested fixes.
  • Workflow support: supports description, analyze, verify, and close phases for end-to-end tracking.

Quick Start

Describe a bug from user input or analyze code to identify issues, then generate a complete bug report ready for QA.

Frequently Asked Questions about bug-report

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

FAQPage Schema
How do I generate a structured bug report from an informal description?▼

To generate a structured bug report, provide an informal bug description and the tool applies a standardized template to capture reproduction steps, severity, evidence, and classification for QA tracking.

Can I analyze code to find potential bugs automatically?▼

Yes, you can analyze code to automatically surface potential bugs and suggested fixes by reading target files and applying a structured triage workflow to identify issues in your codebase.

What is the best way to document reproduction steps for a codebase issue?▼

The best way to document reproduction steps is using a structured bug report template that captures context, evidence, and severity, ensuring the issue is auditable and ready for QA verification.

Does this bug tracking workflow support the full lifecycle from description to closure?▼

Yes, the bug tracking workflow supports a complete multi-phase lifecycle including description, analyze, verify, and close phases to ensure end-to-end issue resolution and tracking.

How do I classify bug severity when documenting code observations?▼

You can classify bug severity by applying a standardized bug report template to your code observations, which systematically captures evidence and context to determine the appropriate severity classification.

Related Skills

Explore More Software Engineering Skills→
Synthesys-LabSynthesys-Lab
56

Debugging Report

Diagnose failing tests and generate structured bug reports.

Official
Basic
KentoShimizuKentoShimizu
7

security-vulnerability-management

Prioritize and drive vulnerabilities from SAST/DAST scans to closure.

Community
Advanced
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic
gofhirgofhir
2

go-code-review

Analyze Go source code with golangci-lint and go vet for bugs and race conditions.

Official
Intermediate