Home

git-task wiki

git-task is a git-native task manager. Tasks live inside a repository as git objects under refs/tasks/*: no working-tree files, full history, and the same push/pull model as any other ref. Nothing beyond a normal git repo is required to run it, and there is no server to stand up before you can create your first task.

Two binaries ship from the same codebase: git-task (so git task <command> works as a git subcommand) and gtask (a standalone alias, e.g. gtask ls). The two are interchangeable; use whichever fits your muscle memory.

Where to start

• New to git-task? Start with Installation and Getting Started.
• Want to understand how tasks are stored and synced before relying on it? Read Core Concepts.
• Looking for a specific command? See Task Management and Epics and Links.
• Setting field requirements, or writing rules that fire on task events? See Configuration and Automation.
• Working across several repositories, or syncing tasks between machines? See Sync and Multi-Repo.
• Building a script, dashboard, or bot on top of git-task? Start with JSON Output, then Web Server Integration.
• Using a coding agent (Claude Code and similar) in a repo tracked with git-task? See Agent Skills.
• Contributing to git-task itself? See Development.

Pages

• Installation
• Getting Started
• Core Concepts
• Task Management
• Epics and Links
• Configuration
• Automation
• Sync and Multi-Repo
• JSON Output
• Web Server Integration
• Agent Skills
• Development

The core loop, if you just want a taste

git task new "Fix login timeout" --kind bug --priority high
git task ls
git task show <id>
git task status <id> doing
git task comment <id> "found the root cause"

Every command above also accepts --format json for scripting; see JSON Output.