Skip to content

dedalus-labs/wingman / .agents/skills/issue

Create a GitHub issue using the wingman issue templates (bug, feature). Injects branch and commit context automatically.

Context (auto-detected from HEAD)

  • Current branch: !git branch --show-current
  • Last commit: !git log -1 --oneline
  • Remote: !git remote get-url origin

Template Selection

Parse the first positional arg from $ARGUMENTS as the issue type:

TypeTemplate fileLabels
bug.github/ISSUE_TEMPLATE/bug_report.ymlbug,triage
feature.github/ISSUE_TEMPLATE/feature_request.ymlenhancement

The bug_report.yml file is a GitHub issue form. gh issue create --body submits plain markdown, so translate the yaml form fields into a markdown body with the same section headings (Bug Description, Steps to Reproduce, Expected Behavior, Environment, Additional Context).

For feature_request.yml, read the file and translate form fields the same way.

Rules

  • Issue title: short, imperative, no period, under 80 chars. No conventional-commit prefix (that's for PRs, not issues).
  • The remaining positional args from $ARGUMENTS (after the type) form the title.
  • Use gh issue create --title "..." --body "$(cat <<'EOF' ... EOF)" --label "...".
  • Labels come from the table above. Do not invent new labels.

Task

  1. Parse $ARGUMENTS:
    • First token: issue type (bug or feature). If missing or invalid, ask the user which template to use.
    • Remaining tokens: title.
  2. Read the matching template file from .github/ISSUE_TEMPLATE/.
  3. Fill every section. Leave no placeholder text. If a section truly has no content, write "N/A" rather than deleting the section.
  4. Auto-inject the branch and last-commit context into "Additional Context".
  5. Run gh issue create with the right labels.
  6. Return the issue URL.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 319kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 319kUpdated Claude CodeCodexVerifiedInstall