alex/g3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ask all agents to commit their work

Browse Source
This commit is contained in:
Dhanji R. Prasanna
2026-01-07 09:31:02 +11:00
parent 5d20da2609
commit ff08a622eb
4 changed files with 28 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
agents/euler.md
View File

@@ -156,3 +156,11 @@ These artifacts are useful for understanding coupling, planning refactors, and i
Do NOT include key findings, metrics, or recommendations in AGENTS.md.
The artifacts themselves contain the detailed analysis.
------------------------------------------------------------
COMMIT CHANGES WHEN DONE
When you're done, and have a high degree of confidence, commit your changes:
- Into a single, atomic commit
- Clearly labeled as having been authored by you
- The commit message should include a concise, comprehensive summary of the work you did
- Do NOT check in any separate "summary" files (other than those listed in the artifacts section above)

7
agents/fowler.md
View File

@@ -124,6 +124,13 @@ E) Verify
- confirm new and existing tests pass
- ensure no behavior drift
F) Commit
When you're done, and have a high degree of confidence, commit your changes:
- Into a single, atomic commit
- Clearly labeled as having been authored by you
- The commit message should include a concise, comprehensive summary of the work you did
- Do NOT check in any separate "report" files
CODE-PATH ALIASING (HIGHEST-PRIORITY FAILURE MODE)
You must:

7
agents/hopper.md
View File

@@ -79,6 +79,13 @@ When a subsystem is significant but lacks a stable outer surface:
- Label these as CHARACTERIZATION (not a normative spec).
- Prefer testing at the highest boundary available (module API > helper function).
5) COMMIT CHANGES WHEN DONE **IFF** CONFIDENT IN THEM
When you're done, and have a high degree of confidence, commit your changes:
- Into a single, atomic commit
- Clearly labeled as having been authored by you
- The commit message should include a concise, comprehensive summary of the work you did
- Do NOT check in any separate "summary report" files
------------------------------------------------------------
REPORTING DISCIPLINE

6
agents/lamport.md
View File

@@ -228,6 +228,12 @@ K. Known Limitations / Open Questions (Optional but Recommended)
L. License and Contributing
- Link to LICENSE and CONTRIBUTING if present
4) Commit changes
When you're done, and have a high degree of confidence, commit your changes:
- Into a single, atomic commit
- Clearly labeled as having been authored by you
- The commit message should include a concise, comprehensive summary of the work you did
------------------------------------------------------------
docs/ SECONDARY DOCUMENTATION