implement-ticket

Implement GitHub project tickets end-to-end and open a linked pull request.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/polikeiji/skills --skill implement-ticket-polikeiji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-ticket
Source: https://github.com/polikeiji/skills/tree/main/skills/implement-ticket
Command: npx skills add https://github.com/polikeiji/skills --skill implement-ticket-polikeiji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a GitHub ticket into a finished, reviewable change by guiding the full implementation workflow from reading the issue to opening the pull request. It helps avoid missed subtasks, inconsistent status updates, and incomplete handoffs in project-board-driven development.

Core Features & Use Cases

  • End-to-End Ticket Execution: Reads the parent issue, extracts objectives, acceptance criteria, and sub-items, then works through the implementation in order.
  • Project Board Coordination: Updates GitHub Project item status for the parent issue and sub-issues so progress stays synchronized with the board.
  • Commit and PR Discipline: Creates a branch, commits per sub-item, links work to the correct issue, and opens a single PR for review.
  • Use Case: A developer assigns an issue from a GitHub Projects board and wants the assistant to carry it through implementation, status tracking, and PR creation without losing traceability.

Quick Start

Ask the assistant to implement a specific GitHub issue or project ticket end-to-end and provide the issue number or URL.

Frequently Asked Questions about implement-ticket

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue implementation end-to-end from project board to pull request?

To automate GitHub issue implementation end-to-end, this Skill reads the parent issue and sub-items, executes the changes in order, and opens a linked pull request. It coordinates GitHub Projects board status updates and commits changes per sub-item to maintain traceability.

How does issue-driven development work with GitHub Projects and child issues?

Issue-driven development with GitHub Projects breaks parent tickets into child issues or task-list checkboxes. This Skill parses that structured hierarchy, implements the work sequentially, and updates project board item statuses automatically to keep progress synchronized.

Do I need GitHub CLI authentication to automate branch workflow and PR creation?

Yes, GitHub CLI authentication is required to automate branch workflow and PR creation. The Skill relies on the GitHub CLI to read issue details, create branches, commit changes, update project board statuses, and open pull requests referencing the parent ticket.

What is the best way to track sub-task progress in GitHub Projects during implementation?

The best way to track sub-task progress in GitHub Projects during implementation is by updating item statuses directly through the workflow. This Skill automatically synchronizes parent and child issue statuses on the project board as it commits changes per sub-item.

Can I use this approach for issue-driven development if my tickets only use task-list checkboxes instead of child issues?

Yes, you can use this approach for issue-driven development with task-list checkboxes. The Skill supports workflows that use GitHub Projects, child issues, or task-list checkboxes to break work into ordered implementation steps.

Why does my GitHub project board status stay out of sync when I implement issues manually?

GitHub project board status stays out of sync during manual implementation because developers often forget to update item statuses after committing. This Skill automates project board coordination, updating parent and sub-issue statuses as it progresses through the implementation.