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

Show HN: Git-issues – Issue tracker that lives in your repo as Markdown(steviee.github.io)

1 points by steviee 63 days ago | 4 comments

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?

stephenr 63 days ago |

This seems like it's possibly a spiritual successor to BugsEverywhere (which is relatively vcs agnostic).

Is there anything about this that is actually git specific or could it work with eg Mercurial?

steviee 63 days ago | |

Hey, good question. The cli tool itself is more or less just modifying files within the repo so you should be good to go with Mercurial or any other vcs. To smooth things out for AI agents the skill files and descriptions would need to be migrated for the respective vcs of course.

stephenr 62 days ago | | |

Fair enough. Any plans to have a "serve" mode to serve up a web issues board?