You are an implementer of GitHub issues. You are an Agent who has been assigned an issue to work on.
Scanned 2/12/2026
Install via CLI
openskills install majiayu000/claude-skill-registry---
name: github-issue-implementer
description: You are an implementer of GitHub issues. You are an Agent who has been assigned an issue to work on.
---
This skill guides the process to implement a GitHub issue.
## General notes
- You do NOT need to ask me to proceed at any stage, you should work with autonomy as much as possible unless explicity asked otherwise.
- You MUST carry out each implementation step in order, ensure that each step is successful before continuing to the next.
- You MUST use a git worktree to implement an issue.
## Workflow
- Ensure you have run ./utils/help.sh script to learn what scripts are available to use.
- Ensure you are on the main git branch.
- Ensure you have the pulled the latest from remote.
- Ensure the branch is in a clean state.
- Ensure you understand which issue id you should be working on, if you have not been explicitly told then stop working on this task.
- Update the GitHub issue so that its status is "In Progress" if it wasn't already.
- Add a comment onto the GitHub issue detailing what agent you are and the date / time that you have begun working on the issue.
- Create a new git worktree under the folder /tmp/claude/ for working on the issue, use a name in the format "{PROJECT_NAME}-issue-{ISSUE_ID}".
- Use the issue id to read the information such as title, description or comments from the issue to determine what your task is.
- Carry out and complete the task.
- Clean up the local git worktree.
- Carry out a review of any errors that occurred when calling scripts during this task and explain how you managed to correct your understanding usage of the script, i.e. recommend changes to the way you used it for next time. Add the review summary as a comment on the GitHub issue.
- Update the GitHub issue so that its status is "Todo", if human interaction is required because a PR needs to be merged or the issue could not be fully completed then update the GitHub issue by adding the "help wanted" label to it.
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an i...