SuperAPI AI Directory

gh-issue-autodev

General & other

View repository

Updated 10-16 06:16

About this skill

GitHub Issue Auto Dev

Overview

Resolve one GitHub issue completely in the current repository from intake to pushed commit.

Inputs

  • issue_number (required)
  • Optional constraints from user (scope boundaries, deadlines, must-have behavior)

If issue_number is missing, ask for it and stop until provided.

Workflow

  1. Preflight checks
  • Confirm repo context with pwd, git rev-parse --show-toplevel, and git rev-parse --abbrev-ref HEAD.
  • If branch is main or dev, stop and ask the user to switch to a working branch.
  • Run gh auth status; if unauthenticated, ask the user to run gh auth login first.
  1. Load and understand the issue
  • Run gh issue view <issue_number> --json number,title,body,labels,assignees,state,url.
  • Classify the issue: requirement, defect, or other task.
  • Extract acceptance criteria, constraints, and edge cases.
  1. Ambiguity gate
  • If expected behavior, scope, or acceptance criteria is ambiguous, ask the user concise clarification questions.
  • Do not start implementation until ambiguities are resolved.
  1. Decompose when needed
  • If work is non-trivial (multi-module, high-risk, or multi-step), produce a short execution plan and then implement step-by-step.
  1. Implement the fix or feature
  • Make only necessary changes tied to the issue.
  • Keep diffs small and focused.
  1. Verify quality
  • Pick checks based on changed surface area:
  • Frontend/TS changes: run lint + typecheck + relevant tests.
  • Backend/functions changes: run lint + unit/integration tests for impacted modules.
  • Build/config changes: run impacted build and validation commands.
  • Automatically run the $playwright skill when UI validation is necessary, and verify critical user paths.
  • Do not use Playwright MCP for this workflow.
  • Escalate to $playwright-interactive only when the issue requires persistent local browser state across edits, repeated reloads, or Electron validation.
  • For authenticated TaleDraw or TaleLens console UI checks, first run source "$HOME/.config/taledraw-test.env" when the file exists. Then prefer TALEDRAW_TEST_EMAIL and TALEDRAW_TEST_PASSWORD; if they are unset, fall back to TALELENS_TEST_EMAIL and TALELENS_TEST_PASSWORD. If env vars are still missing, use Keychain (codex-talelens-test-email / codex-talelens-test-password). Do not hardcode credentials in repo files.
  1. Commit and push
  • Review with git status and a focused diff summary.
  • Commit using Conventional Commits with issue context.
  • Push only the current branch: git push origin <current-branch>.
  1. Final report
  • Return issue URL, problem summary, implemented changes, verification commands/results, and commit SHA.
  • If any check could not run, state why and list residual risk.

Command Snippets

  • gh issue view <issue_number> --json number,title,body,labels,assignees,state,url
  • gh issue view <issue_number> --web
  • git rev-parse --abbrev-ref HEAD
  • git status