nhcarrigan/hikari-desktop
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 9 Pull Requests 36 Actions Releases 22 Activity

feat: auto-commit after task completion in task loop #192

New Issue
Closed
opened 2026-03-06 09:39:06 -08:00 by hikari · 0 comments
hikari commented 2026-03-06 09:39:06 -08:00
Owner
Copy Link
Copy Source

Overview

Inspired by get-shit-done (GSD)'s atomic git commits per task, this adds an optional auto-commit feature to the Task Loop (#183) — automatically committing completed task work before advancing to the next task.

The Problem: Lost Context

Without atomic commits, a long autonomous task run produces a single large diff with no meaningful history. If something goes wrong mid-run, it's hard to identify which task introduced the issue or to roll back selectively.

Feature Details

Behaviour

When auto-commit is enabled and a task completes successfully:

  1. Claude runs git add -A in the working directory
  2. Claude commits with a generated message based on the task title
  3. The task is marked complete and the loop advances
  4. If the git commit fails (e.g. nothing to commit, git not initialised), the task is still marked complete and the loop advances — the commit failure is logged but non-blocking

Commit Message Format

Auto-generated commit messages follow conventional commit format:

feat: <task title>

Auto-committed by Hikari Task Loop
Task ID: <task-id>
Loop session: <session-timestamp>

Configuration Options

In the Task Loop panel settings:

  • Auto-commit toggle (off by default)
  • Commit message prefix — customise the conventional commit type (feat/fix/chore/etc.)
  • Include task summary — optionally append Claude's task summary to the commit body
  • Sign commits — use the configured git signing key (respects existing git config)

SUMMARY.md Generation

Before committing, optionally ask Claude to write a brief SUMMARY.md (or append to an existing one) describing:

  • What was implemented
  • Key decisions made
  • Files changed
  • Any caveats or follow-up work

This SUMMARY.md is then included in the commit and can update STATE.md in the Project Context Panel (#188).

Safety Guardrails

  • Auto-commit only triggers on task success, never on error
  • Prompts user for confirmation if there are unexpected file changes (files outside the working directory)
  • Can be paused at any time without affecting current task

Acceptance Criteria

  • Auto-commit toggle available in Task Loop settings
  • Successful tasks trigger git add -A + git commit in the working directory
  • Commit message follows conventional commit format with task metadata
  • Git failures are logged but non-blocking (loop still advances)
  • SUMMARY.md generation is optional and configurable
  • Commit message prefix is customisable
  • Only triggers on successful task completion, never on error
  • Tests written for commit message generation logic

✨ This issue was created with help from Hikari~ 🌸

## Overview Inspired by [get-shit-done (GSD)](https://github.com/gsd-build/get-shit-done)'s **atomic git commits per task**, this adds an optional **auto-commit** feature to the Task Loop (#183) — automatically committing completed task work before advancing to the next task. ## The Problem: Lost Context Without atomic commits, a long autonomous task run produces a single large diff with no meaningful history. If something goes wrong mid-run, it's hard to identify which task introduced the issue or to roll back selectively. ## Feature Details ### Behaviour When auto-commit is enabled and a task completes successfully: 1. Claude runs `git add -A` in the working directory 2. Claude commits with a generated message based on the task title 3. The task is marked complete and the loop advances 4. If the git commit fails (e.g. nothing to commit, git not initialised), the task is still marked complete and the loop advances — the commit failure is logged but non-blocking ### Commit Message Format Auto-generated commit messages follow conventional commit format: ``` feat: <task title> Auto-committed by Hikari Task Loop Task ID: <task-id> Loop session: <session-timestamp> ``` ### Configuration Options In the Task Loop panel settings: - **Auto-commit** toggle (off by default) - **Commit message prefix** — customise the conventional commit type (feat/fix/chore/etc.) - **Include task summary** — optionally append Claude's task summary to the commit body - **Sign commits** — use the configured git signing key (respects existing git config) ### SUMMARY.md Generation Before committing, optionally ask Claude to write a brief `SUMMARY.md` (or append to an existing one) describing: - What was implemented - Key decisions made - Files changed - Any caveats or follow-up work This SUMMARY.md is then included in the commit and can update STATE.md in the Project Context Panel (#188). ### Safety Guardrails - Auto-commit only triggers on task `success`, never on `error` - Prompts user for confirmation if there are unexpected file changes (files outside the working directory) - Can be paused at any time without affecting current task ## Acceptance Criteria - [ ] Auto-commit toggle available in Task Loop settings - [ ] Successful tasks trigger `git add -A` + `git commit` in the working directory - [ ] Commit message follows conventional commit format with task metadata - [ ] Git failures are logged but non-blocking (loop still advances) - [ ] SUMMARY.md generation is optional and configurable - [ ] Commit message prefix is customisable - [ ] Only triggers on successful task completion, never on error - [ ] Tests written for commit message generation logic ✨ This issue was created with help from Hikari~ 🌸
naomi closed this issue 2026-03-07 03:08:34 -08:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/hikari-desktop#192
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?