Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →codelytv/codely-plan_phase-implement-github
Implement one phase of a plan stored as GitHub issues in the repository of the current working directory. Given the URL of a phase (child) issue it implements that phase; given the parent plan issue it finds and implements the current phase. Only implements a single phase per invocation, then stops for user review. It opens a pull request that references the phase issue so merging it closes the issue automatically. Never merges the pull request.
Passed 5 of 12 test cases with the skill, and 4 of 12 without it.
and 2 more in the full report
5 fixed5 passed either way10 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Phase issue #9 was the final phase of parent plan #2. What post-implementation action should be suggested regarding the user's IDE session?
| Checked | Without skill | With skill |
|---|---|---|
| Suggests exporting the IDE conversation and attaching it as a comment on the parent issue | Missed | Passed |
The instructions your model reads when the skill loads.
[!CRITICAL] Implement ONLY ONE phase per invocation. After completing the current phase, STOP and wait for the user to review the changes. Never proceed to the next phase without explicit user approval.
[!CRITICAL] Never merge the pull request. This skill may create a feature branch, commit, push and open a pull request, but the user decides when to merge. Merging is what closes the phase issue.
This skill is invoked as /codely-plan_phase-implement-github <github-issue-url>. The URL can point to either:
If no URL is provided, ask the user for it before doing anything else.
The plan and its phases live as GitHub issues in the repository of the current working directory, and the pull requests are opened there too. Never hardcode a repository: let gh resolve it from the local Git remote.
gh issue view <number>
gh issue develop <number> --checkout
gh pr create --title "..." --body "..."
Confirm the repository gh resolves with gh repo view --json nameWithOwner --jq .nameWithOwner, and check that the provided URL belongs to it. If it does not, stop and ask the user to run the skill from the clone of that repository: the phase branch must be created in the same repository you are implementing the task in.
gh issue view <url> to read the given issue.Part of #<parent> reference and a to-do checklist), that is the phase to implement.Phases checklist linking child issues), the current phase is the first child issue in that checklist that is still open. Read that child issue and implement it.test cases passed, vs 4 / 12 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.