gitcli-todo

Tracks git tags as a todo list with cursor-based progress and commit queries.

3|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/ZHLX2005/sl --skill gitcli-todo-zhlx2005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitcli-todo
Source: https://github.com/ZHLX2005/sl/tree/main/skills/gitcli-todo
Command: npx skills add https://github.com/ZHLX2005/sl --skill gitcli-todo-zhlx2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing changes across many git tags is hard to track manually. This Skill turns git tags into a checklist so you can see which tags are still pending review, inspect the commits between tags, and mark tags as done without losing your place. ## Core Features & Use Cases - Pending Tag Queries: Run tagcli query -n N to list the next N undoned tags along with the commits since the previous tag. - Progress Tracking: Mark tags as done with tagcli ack <tag> and view overall status with tagcli status; state persists in a .gittags-cursor file. - Use Case: A reviewer auditing a monorepo with 105 release tags runs tagcli query -n 3 each morning, reviews the commits for each tag, acknowledges them, and resumes exactly where they left off the next day. ## Quick Start Ask the assistant to run tagcli query -n 5 in your repository to show the next five pending git tags with their commits.

Frequently Asked Questions about gitcli-todo

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

FAQPage Schema
How do I track git tag review progress across sessions?

Use tagcli to treat git tags as a checklist. Run tagcli query -n N to see pending tags, then tagcli ack <tag> to mark each as done. Progress persists in a .gittags-cursor file so later queries skip completed tags.

How to list commits between two git tags?

Run tagcli query -n N to display each pending tag together with the commits made since the previous tag. Tags are sorted by creation date, earliest first, so commits appear in chronological release order.

Does tagcli require network access or a remote repository?

No, tagcli performs only local git operations with no network calls. It reads tags and commits directly from the local repository, so it works offline against any cloned repo.

Can I use separate progress cursors for different projects?

Yes, the cursor is stored as a .gittags-cursor file in the executable's directory, so each installation maintains its own done list. Build separate tagcli binaries per project to keep independent progress.

How do I reset or reinitialize the tag progress cursor?

Run tagcli reset to clear all done marks and start over, or tagcli init to create a fresh cursor file. After reset, queries will return all tags as pending again.