Bug Report

Bug Report Guide (Non-Interactive)

Follow this guide to create bug reports following Marty conventions. Use /create-issue with the bug template.

Bug Report Process

Step 1: Verify it's a Bug

Before creating a bug report:

• Confirm the issue is reproducible
• Check if it was already reported
• Verify expected behavior

Step 2: Create Issue with Bug Template

gh issue create -t "[bug]: brief description" --body-file "templates/bug.md" -l bug

Step 3: Add Priority Label

# Critical bug
gh issue edit <number> --add-label "priority/p0"

# High priority
gh issue edit <number> --add-label "priority/p1"

Bug Report Template

## Summary
[Brief description of the bug]

## Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Step 3]

## Expected Behavior
[What should happen]

## Actual Behavior
[What actually happens]

## Environment
- OS: [OS version]
- Tool version: [version]

## Possible Cause
[Your guess at what might be causing this]

Co-Authored-By: martyy-code <nesalia.inc@gmail.com>

Bug Severity Levels

Quick Reference

Create bug issue:    gh issue create -t "[bug]: title" --body-file "templates/bug.md" -l bug
Set priority:        gh issue edit <num> --add-label "priority/p1"
Assign self:         gh issue edit <num> --add-assignee "@me"
Add to canary:       gh issue edit <num> --add-label "status/triaged"

Related Skills