Git workflow
AIDEN is designed to work with real Git-based software development.
It is not trying to hide Git. It is trying to make AI work cleanly with it.
Why this matters
A lot of AI tooling feels impressive until you need to merge, review, isolate, or trust the result.
AIDEN stays grounded by keeping implementation close to:
- branches
- worktrees
- review stages
- pull requests
- story boundaries
How it works in practice
- When a story moves into implementation, AIDEN creates a branch for it automatically.
- Parallel work is isolated in Git worktrees, so several stories — and several agents — can run at once without conflicts.
- Commits stay tied to the story that produced them, so progress is traceable.
- When a story is done, AIDEN can open a pull request for it — see the GitHub guide.
Each story ends up feeling like a real unit of engineering work, not just a prompt history.
What this gives you
- cleaner boundaries around active work
- easier review — one story, one branch, one diff
- less confusion when several tasks are moving at once
- a more trustworthy path from AI output to shipped code
Best practice
Use AIDEN to stay disciplined, not to skip discipline.
If the code changed, the review boundary should still be real. If the story is not complete, do not pretend it is.