Select, validate, and prepare GitHub issues for development with git worktrees and pull requests.
npx skills add https://github.com/typemd/typemd --skill resolve-issue-typemd
Please help me install this Agent Skill. Skill: resolve-issue Source: https://github.com/typemd/typemd/tree/main/.claude/skills/resolve-issue Command: npx skills add https://github.com/typemd/typemd --skill resolve-issue-typemd
Many developers waste time manually selecting, validating, and preparing GitHub issues before beginning work, leading to context switching and duplicated effort. This skill automates the entire lifecycle—from issue discovery and pre‑flight checks to workspace setup, implementation planning, and pull‑request creation—so engineers can focus on coding.
Use case example: a developer says “resolve issue #42” and the skill creates a branch, sets up tasks, and opens a PR ready for merge.
Resolve issue #42
High-intent search queries and answers about installing and using this skill.
To automatically turn GitHub issues into pull requests, you can use a skill that orchestrates issue selection, pre-flight validation, workspace setup, and PR creation. It parses issue numbers, creates isolated git worktrees, generates OpenSpec artifacts, and opens a PR ready for merge.
Setting up a git worktree for a specific GitHub issue is handled by automated workspace setup. The process applies pre-flight checks to detect existing branches, establishes proper branch naming conventions, and creates an isolated git worktree for development.
Yes, you can automate BDD task execution from an issue in your devops workflow. The process orders tasks test-first and drives behavior-driven development or sub-agent development directly after generating the initial OpenSpec design artifacts.
The best way to validate a GitHub issue before development is running pre-flight checks. This detects existing OpenSpec changes or branches to avoid conflicts, automatically selecting the highest-priority open issue or parsing version numbers to prepare it.
Yes, the issue resolution process works with the GitHub CLI. It uses git and GitHub CLI tools to automate the entire lifecycle, from issue discovery and workspace setup to running final verification and opening a pull request that closes the targeted issue.
You should avoid automated issue resolution for pull requests when existing OpenSpec changes or branches are detected. The built-in pre-flight validation stops the process to prevent conflicts, meaning manual intervention is required to clear or merge existing workspaces first.
storyclaw-officialOrchestrate parallel sub-agents to fix GitHub issues and open pull requests.
zts212653Automate merge governance from gate checks to cleanup on Git main branches.
baphledEnforce test-first development by mandating failing tests before implementation code.
MoRen9527Orchestrate GitHub issue fixes by spawning sub-agents to create pull requests.
