Lazy Issue

Create a well-structured GitHub issue. Only create issues in repos owned by us.

Ownership Check

gh auth status
gh org list
git remote -v

If not owned by user or their orgs, DO NOT CREATE — ask how to proceed.

Research Phase

Before creating, search for:

• •Similar implementations in other projects
• •Code examples and patterns
• •Best practices and pitfalls
• •Relevant discussions in similar projects

Enrich issue with links to reference implementations and code snippets.

Issue Components

• •Title: Concise summary ("Add support for..." or "Fix error when...")
• •Problem/Context: What needs to be done or what problem exists
• •Acceptance Criteria: Measurable outcomes defining completion
• •Implementation Details (if applicable):
  • •Technical approach
  • •Code references with file paths
  • •External references and examples
• •Tasks: Checkbox list for multi-step issues

Create Issue

gh issue create --title "Issue title" --body "$(cat <<'EOF'
[issue body]
EOF
)"

Add labels with --label bug or --label enhancement as appropriate.

Clarifying Questions

Use ask_questions tool for:

• •Unclear scope or priority
• •Whether to include implementation details
• •Related issues to reference
• •Appropriate labels