implement-ticket-v2

Name: implement-ticket-v2
Availability: InStock
Author: drdatarulz

Automate ticket workflows from branch creation to PR and issue comments.

3|Updated Feb 20, 2026

Search Tags:#automation #git #workflow #github #ticket #pull-request

Ready to run

npx skills add https://github.com/drdatarulz/TI-Engineering-Standards --skill implement-ticket-v2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement-ticket-v2
Source: https://github.com/drdatarulz/TI-Engineering-Standards/tree/main/skills/archive/implement-ticket-v2
Command: npx skills add https://github.com/drdatarulz/TI-Engineering-Standards --skill implement-ticket-v2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual ticket implementation is labor-intensive and error-prone, requiring branch creation, PR management, and status updates across tools.

Core Features & Use Cases

Automates the end-to-end ticket workflow: create a branch, push, open a PR, and post an issue-comment to reflect progress and outcomes.
Supports FIX mode to address review feedback on an existing PR, ensuring changes are tracked and retried without reworking context.
Aligns with TI Engineering Standards by enforcing deterministic Git operations, standardized messaging, and auditable activity.

Quick Start

Create a feature branch for the ticket, push it, open a PR, and post a status comment to the issue.

Frequently Asked Questions about implement-ticket-v2

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?▼

Automating ticket implementation from branch creation to PR requires deterministic GitHub operations that push code, open pull requests, and post issue comments. This enforces standard-compliant messaging and traceable activity for audit and rollback.

Can I use FIX mode to address pull request review feedback without reworking context?▼

FIX mode addresses review feedback on an existing PR by tracking changes and retrying without reworking context. It ensures review feedback is incorporated directly into the ticket workflow while maintaining traceable activity.

What is the best way to enforce standard-compliant messaging in GitHub workflows?▼

Enforcing standard-compliant messaging in GitHub workflows requires deterministic Git operations that automate branch creation, PR openings, and issue comments. This produces traceable activity for audit and rollback across projects.

Does automated ticket implementation work with engineering standards projects requiring ticket-driven changes?▼

Automated ticket implementation works with engineering standards projects by enforcing deterministic GitHub operations. It automates the end-to-end workflow from branch creation to PR and issue comment, ensuring compliance and traceable activity.

How do I post an issue comment to reflect ticket progress and outcomes automatically?▼

Posting an issue comment automatically requires a ticket implementation workflow that opens a PR and updates the issue with progress and outcomes. This enforces deterministic Git operations and standard-compliant messaging for auditable activity.

Why does manual ticket implementation require automation for branch creation and PR management?▼

Manual ticket implementation requires automation because it is labor-intensive and error-prone across branch creation, PR management, and status updates. Automating enforces deterministic Git operations and traceable activity for audit and rollback.