ticgit

Manage Git-versioned issue tracking and project planning via the TicGit CLI.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/hschne/pi-stuff --skill ticgit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticgit
Source: https://github.com/hschne/pi-stuff/tree/main/skills/ticgit
Command: npx skills add https://github.com/hschne/pi-stuff --skill ticgit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ti, python3, and includes scripts (resource) components.

What problem does it solve?

TicGit eliminates the friction of using separate, non-version-controlled issue trackers that break context traceability with your Git codebase, ensuring all project planning, tickets, and requirements live alongside your code for full auditability and alignment.

Core Features & Use Cases

  • Git-native ticket and PRD management: Create, track, and close tickets directly tied to your Git repository, with dedicated writeups for long-form product requirements, specs for implementation details, and structural dependencies for explicit ticket ordering.
  • End-to-end workflow automation: Run agent loops to implement tickets sequentially, verify work, sync ticket data with remote repositories, and migrate existing file-based issue systems to TicGit without losing historical context.
  • Use Case: A development team can slice a product PRD into linked, dependency-ordered tickets, assign implementation specs to each, and run automated loops to implement and verify each ticket until the entire backlog is complete.

Quick Start

Use the ticgit skill to initialize Git-native issue tracking for your current repository and publish your first set of linked project tickets from an existing PRD.

Frequently Asked Questions about ticgit

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

FAQPage Schema
How do I track issues directly in my Git repository?

You can track issues directly in Git by creating tickets and product requirement writeups as version-controlled entries within your repository, ensuring full auditability and context alignment with your codebase.

What is the best way to manage structural dependencies between project tickets?

The best way to manage ticket dependencies is through explicit structural dependency wiring that orders tickets sequentially, enabling automated agent loops to implement and verify each ticket until the backlog is cleared.

Can I migrate existing file-based issue systems to a Git-integrated tracker?

Yes, you can migrate file-based issue systems to a Git-integrated tracker using the CLI. This migrates existing issues into version-controlled tickets and syncs data with remote repositories without losing historical context.

Do I need Python to run automated backlog processing for Git tickets?

Yes, Python is required to run the scripts that automate backlog processing. These scripts drive agent loops to sequentially implement tickets, verify work, and sync ticket data with remote repositories.

How do I automate implementation handoffs for a product requirement document?

You can automate implementation handoffs by slicing a product requirement document into linked tickets with assigned implementation specs, then running automated agent loops to implement and verify each ticket sequentially.

Why use Git-native ticket tracking instead of separate project management tools?

Git-native ticket tracking ensures all project planning, tickets, and requirements live alongside your code for full auditability and context alignment, eliminating the traceability breaks caused by separate project management tools.