← ClaudeAtlas

ginee-file-buglisted

File a bug report against the primary GitHub repo (the adopter's own project) via the ginee framework's GitHub-integration workflow. Use when the user asks to 'file a bug', 'report a bug', 'create a bug issue' for the current project. Drafts a structured issue using core/templates/issues/bug-report.md, surfaces the draft for approval, then creates a labelled GitHub issue.
kostiantyn-matsebora/ginee · ★ 0 · AI & Automation · score 68
Install: claude install-skill kostiantyn-matsebora/ginee
# File bug — primary repo Run the file-an-issue workflow per `.agents/ginee/core/protocols/github-integration.md § Outbound — file an issue` with target = primary repo. ## Activation - User asks to "file a bug" / "report a bug" / "create a bug issue" without mentioning the framework upstream. - User describes a defect and explicitly wants it tracked in their own repo. ## Procedure 1. Load `.agents/ginee/core/protocols/github-integration.md` and `.agents/ginee/core/templates/issues/bug-report.md`. 2. Resolve target repo: - Override: `local/framework.config.yaml § github.repo`. - Else: `git remote get-url origin` (strip `.git`). 3. Draft the issue body from the bug-report template. Populate every section (`## Summary`, `## Steps to reproduce`, `## Expected behavior`, `## Actual behavior`, `## Affected area`, `## FR / NFR cited`, `## Acceptance criteria`, `## Reporter context`) from user prompt + project context. 4. **Self-lint the draft** against `.agents/ginee/core/process.md § Mandatory checks before report-as-done` — **every section, including Summary**. Catch: prose paragraphs > 2 sentence terminators · comma-separated inventories (incl. parenthetical lists) · multi-rule single-line statements · inventories not rendered as tables. Surface violations as restructure suggestions in step 5; never publish a body that fails self-lint without explicit user override. 5. **Surface the draft for user approval** — issues are externally visible per `.agents/ginee/core/proces