bug

Create structured bug reports and optional VK tickets in the .agent workspace.

Updated Mar 6, 2015

Search Tags:#documentation #QA #bug-tracking #bug-reporting #feature-linking #VK-ticket

Ready to run

npx skills add https://github.com/yoaquim/.dotfiles --skill bug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug
Source: https://github.com/yoaquim/.dotfiles/tree/main/claude/skills/bug
Command: npx skills add https://github.com/yoaquim/.dotfiles --skill bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes bug reporting and integrates optional VK ticket creation, helping teams capture issues quickly and consistently.

Core Features & Use Cases

Bug documentation: Create structured bug reports with title, summary, steps to reproduce, severity, and attachments.
Feature linkage: Tie bugs to a specific feature when a recent feature is identified.
VK ticket automation: Optionally generate VK tickets for tracked bugs to coordinate with development.

Quick Start

Run the following commands to document a bug:

/bug 001 to tie the bug to feature 001 → .agent/features/001-{name}/bugs/
/bug to create a standalone bug → .agent/bugs/

Frequently Asked Questions about bug

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

FAQPage Schema

How do I create structured bug reports with documentation?▼

Bug documentation captures title, summary, steps to reproduce, severity, and attachments in a standardized format. Run `/bug` to create a standalone bug report organized under .agent/bugs/, or `/bug 001` to tie it to a specific feature under .agent/features/001-{name}/bugs/.

Can I automatically create VK tickets from bug reports?▼

Yes. This Skill automates VK ticket creation from structured bug reports when requested, coordinating tracked bugs with development workflows and centralizing issue tracking.

What's the best way to organize bugs across multiple features?▼

Link bugs to features using `/bug 001` syntax to nest bug reports under specific feature directories, or use `/bug` for standalone bugs. This enforces consistent documentation hierarchy across the .agent workspace.

Do I need VK integration to use bug documentation?▼

No. VK ticket creation is optional. You can document bugs with full structure—title, summary, reproduction steps, severity, and attachments—without triggering ticket automation.

How does feature linkage help with bug tracking?▼

Feature linkage ties bugs to specific features, organizing reports hierarchically and establishing traceability between issues and the features they affect.