implement-ticket-v3

Automate GitHub ticket implementation from branch creation to pull request.

3|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/drdatarulz/TI-Engineering-Standards --skill implement-ticket-v3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-ticket-v3
Source: https://github.com/drdatarulz/TI-Engineering-Standards/tree/main/skills/archive/implement-ticket-v3
Command: npx skills add https://github.com/drdatarulz/TI-Engineering-Standards --skill implement-ticket-v3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end process of implementing a single ticket: creating a dedicated branch, pushing changes, opening a pull request, and posting a summary on the issue to streamline reviews.

Core Features & Use Cases

  • End-to-end ticket workflow: from branch creation to PR and issue comment, reducing manual steps.
  • Review-ready automation: supports FIX mode to address review feedback on an existing PR.
  • Context-aware execution: reads ticket details, determines the branch name, and executes GitHub operations consistently.

Quick Start

Create a new branch for the ticket, implement the changes per the ticket, push the branch, and open a pull request titled with the ticket and a summary comment.

Frequently Asked Questions about implement-ticket-v3

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

FAQPage Schema
How do I automate GitHub ticket implementation from branch creation to pull request?

Automate GitHub ticket implementation by creating a dedicated branch, pushing changes, opening a pull request titled with the ticket details, and posting a summary comment on the issue for streamlined reviews.

Can I automatically address pull request review feedback using a GitHub workflow?

You can address pull request review feedback automatically using FIX mode, which handles review comments on an existing PR to streamline iterative updates within the GitHub workflow.

How does context-aware execution work for automating GitHub issue branches?

Context-aware execution reads ticket details to determine the repository context, automatically extracts story details, and executes consistent Git operations for branch naming based on the issue.

What is the end-to-end workflow for creating a pull request from a GitHub ticket?

The end-to-end workflow for creating a pull request involves determining the repository context, creating a dedicated branch, implementing changes, pushing the branch, and opening a pull request with an issue summary comment.

Do I need to manually post status updates to a GitHub issue after opening a pull request?

You do not need to manually post status updates to a GitHub issue; the automation handles posting summary comments and status updates back to the issue after opening the pull request.