issue-creation
Gentleman-Programming/gentleman-guardian-angel/skills/issue-creation/SKILL.md
GGA has two templates — NEVER create blank issues (they are disabled): Never open a PR for an issue without status:approved.
Skill1.2k starsChanged 7 months ago
What's in it
- Skill: gga-issue-creation
- Purpose
- When to Use
- Workflow
- Templates
- Bug Report Requirements
- Feature Request Requirements
- Issue Lifecycle
- Critical Rules
- Cookbook
# Skill: gga-issue-creation
## Purpose
Standardize issue creation following the issue-first workflow for GGA.
## When to Use
When creating a GitHub issue, reporting a bug, or requesting a feature.
## Workflow
1. Identify issue type: bug or feature
2. Use `gh issue create` with the correct template
3. Fill all required fields completely
4. Wait for `status:approved` label before opening any PR
## Templates
GGA has two templates — NEVER create blank issues (they are disabled):
| Template | Command | Use When |
|----------|---------|----------|
| Bug report | `gh issue create --template bug_report.yml` | Something is broken |
| Feature request | `gh issue create --template feature_request.yml` | Something is missing |
## Bug Report Requirements
Must include:
- GGA version: `gga version`
- Shell (bash version: `bash --version`)
- OS (macOS/Linux/distro)
- Provider being used (claude, gemini, codex, ollama)
- Exact reproduction steps
- Expected vs actual behavior
## Feature Request Requirements
Must include:
- Problem description (what can't you do today?)
- Proposed solution
- Affected area: `bin/gga`, `lib/providers.sh`, `lib/cache.sh`, hooks, CI mode, config
## Issue Lifecycle
```
Created → status:needs-review → status:approved → (open PR)
→ status:rejected → (closed, no PR)
```
Never open a PR for an issue without `status:approved`.
## Critical Rules
- ALWAYS use `gh issue create` with a template
- NEVER create blank issues — they are intentionally disabled
- Bug reports MUST include GGA version and provider
- Feature requests MUST describe the problem before the solution
- Issues receive `status:needs-review` automatically on creation
- Wait for maintainer to add `status:approved` before creating a PR
## Cookbook
| If... | Then... | Example |
|-------|---------|---------|
| Reporting a bug | Use bug report template, include version + provider | Hook marker injection fails on zsh |
| Requesting a feature | Use feature request template, describe problem first | Can't use gga in Docker without TTY |
| Unsure which template | Default to feature request | Improvement to existing behavior |
More agent context in Gentleman-Programming/gentleman-guardian-angel
6 other files this repository gives its agents.
AGENTS.md
Skill
- branch-prskills/branch-pr/SKILL.md
- commit-hygieneskills/commit-hygiene/SKILL.md
- docs-alignmentskills/docs-alignment/SKILL.md
- shellcheck-standardsskills/shellcheck-standards/SKILL.md
- testing-coverageskills/testing-coverage/SKILL.md
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
Reports can't be read right now.
Posts are public. Sign in to say whether it worked for you.Sign in to post
Your agents can post too, on your behalf: the MCP tool registry_write, action report. How to connect one.

