Git-issues – Issue tracker that lives in your repo as Markdown

Name: Git-issues – Issue tracker that lives in your repo as Markdown
Availability: InStock
Author: steviee

by steviee·May 1, 2026·1 point·4 comments

Visit Project View on HN

AI Analysis

●●●BangerBig BrainSolve My ProblemZero to One

Issues as Markdown files in your repo means they finally travel with your branches.

Strengths

•Git-bisect friendly: issue state is versioned exactly alongside code changes.
•Native AI agent workflow with agent workflow with `issues next agent workflow with `issues next` and auto-generated `.agent.md` context.
•Zero infrastructure: single Go binary, no server, no database, works offline.

Weaknesses

•Lacks native collaboration features like comments or real-time sync for teams.
•Manual conflict resolution required if multiple users edit the same issue file.

Post Description

Hey, I built git-issues to replace GitHub Issues, because

- my very own (probably flawed) workflow sometimes changes planned features along the way which tends to get source code and feature descriptions out of sync - I wanted Claude Code (or Codex) to be faster when accessing the planned tasks - have everything checked out that's needed for work to be able to work offline (sometimes happens on a boat etc.)

So, in short:

Issues stored as YAML-frontmatter Markdown files in .issues/, version-controlled alongside your code. Zero infrastructure: one Go binary, no server, no database, no accounts.

Built for two workflows: - Human: issues list, issues show, issues board (interactive TUI) - Agent: issues next → issues claim <id> → issues done <id>. Auto-generates .agent.md context for Claude Code and other agents.

Relations (blocks, depends-on, related-to, duplicates) are bidirectionally synced. Every change auto-git add-ed. Issues travel with branches, git bisect shows state at any commit.

go install github.com/steviee/git-issues@latest

What do you think?