Convert a GitHub issue into a review-ready pull request with a plan-then-implement workflow.
npx skills add https://github.com/Garsdal/Dojo --skill solve-issue-garsdal
Please help me install this Agent Skill. Skill: solve-issue Source: https://github.com/Garsdal/Dojo/tree/main/.claude/skills/solve-issue Command: npx skills add https://github.com/Garsdal/Dojo --skill solve-issue-garsdal
It helps you move a GitHub issue from filed status to an open pull request ready for human review by planning changes first and then implementing them on a feature branch.
<type>/issue-<N>-<slug> pattern and opens a PR that includes the correct “Closes #<N>” line.docs/RELEASING.md is present, performs the required semver bump and changelog updates including agent prompt notes.Run the solve-issue skill for a specific GitHub issue number or URL, review the generated plan.md, then run the same skill again to implement and open the PR.
High-intent search queries and answers about installing and using this skill.
You can convert a GitHub issue into a pull request by running an automated workflow that researches the codebase, generates an implementation plan, creates a feature branch, codes the changes, and opens a PR with a Closes #<N> line.
The best way to plan codebase changes before opening a PR is to use a plan-then-implement flow that reads referenced files, explores callers and callees, checks related tests, and pauses for user approval before writing code on a feature branch.
Yes, you can automatically create a feature branch and link it to a GitHub issue. The process creates a branch following a specific naming pattern and ensures the resulting pull request includes a load-bearing Closes #<N> line to link the issue.
Automated issue resolution handles version bumps by checking for release documentation. If release docs exist, it performs the required semver bump and updates the changelog with agent prompt notes before opening the pull request.
Yes, the issue-to-PR workflow requires manual code review before implementation. It follows a two-phase design that generates a plan to a deterministic path and pauses for user approval before proceeding to implement the actual code changes.
tim-hubFetch Jira ticket data and generate a structured development plan.
Hoang604Review and refine a phase plan in PLAN.md before execution.
intelligentcode-aiAutomates version bumps, changelog updates, PR merges, tagging, and GitHub releases.
kristofferrembackUpdate GitHub pull request descriptions with structured problem and solution sections.