feat: v0.1.4 - Fix commit message quality, progress verbosity, and task history persistence #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR implements the v0.1.4 remediation plan addressing 4 issues identified during testing of v0.1.3 in the demo repository.
Issues Resolved
🔴 Issue 1: Commit Message Quality
Problem: Commit messages contained conversational preambles ("I'll check...") and were truncated mid-word.
Solution:
[COMMIT_MESSAGE]block in agent prompts for explicit commit messagesextractSummary()with fallback chaintruncateAtWord()helper to avoid mid-word cuts🔴 Issue 2: Progress Verbosity Config Not Applied
Problem:
progressVerbosityconfig was ignored;standardshowed same output asminimal.Solution:
rawResponseandactionsin iteration records during loop executionformatIteration()to show actions atstandardverbosity levelfullverbosity now shows raw AI response in addition to actions🟡 Issue 3: Progress File Not Persisting Task History
Problem: After multi-task runs, progress file only showed the last task (previous tasks lost).
Solution:
save()withsetCurrentTask()for iteration updatesappendTaskResult()withrecordTaskCompletion()for task completion🟡 Issue 4: Push Reminder Message
Problem: Users unaware their changes weren't pushed when
autoPush: false.Solution:
Files Changed
src/core/prompt-examples.ts[COMMIT_MESSAGE]block and examplessrc/core/context-builder.tssrc/core/loop-engine.tsextractSummary()rewrite,rawResponse/actionscapturesrc/core/checkpoint-manager.tssrc/core/progress-tracker.tssrc/commands/run.tsREADME.mdprogressVerbositydescriptiondocs/cookbook.mddocs/architecture.mdTesting
npm run build- Compiles successfullynpm run lint- No linting errorsnpm run test- 311 tests passingVersion
Bumped to v0.1.4
Related
plans/v0-1-4_REMEDIATION_PLAN.md