dirtydishes/islandflow
1
0
Fork 0
Code Issues 2 Pull requests 4 Projects Releases Packages Wiki Activity Actions 1

default turn-doc diffs to @pierre/diffs and add dependency
Some checks are pending
Discord notifications / Push -> Discord (main) (push) Waiting to run
Details
Discord notifications / CI result -> Discord (red on failure) (push) Waiting to run
Details
Discord notifications / Release -> Discord (lavender) (push) Waiting to run
Details

Browse source
This commit is contained in:
dirtydishes 2026-05-23 18:52:15 -04:00
parent 5ff2fa6d2c
commit 4a0e9e7fe1
4 changed files with 109 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
AGENTS.md
View file

@ -90,6 +90,8 @@ At the end of every completed implementation task, before final handoff, create
This documentation is mandatory whenever code, configuration, tests, or project files were changed.
For diff content in turn documentation (including "Code diffs" and "Relevant Diff Snippets"), use `@pierre/diffs` output by default. If `@pierre/diffs` is unavailable because of a real tool or blocking error, use a clearly labeled plain diff/code block fallback and note why.
### Do not produce this for minor or trivial changes, including but not limited to:
- Syntax fixes
@ -105,7 +107,7 @@ This documentation is mandatory whenever code, configuration, tests, or project
**"New Changes as of {time and date at which the change was made}"**
- **Summary of changes**
- **Why this change was made**
- **Code diffs**
- **Code diffs** (use `@pierre/diffs` output by default; if unavailable, include a clearly labeled plain diff/code block and note why)
- **Related issues or PRs**
Additionally, add a note to each section explaining why the changes were made.
@ -154,7 +156,7 @@ Each turn document must include these sections:
2. **Changes Made**
3. **Context**
4. **Important Implementation Details**
5. **Relevant Diff Snippets**
5. **Relevant Diff Snippets** (render with `@pierre/diffs` output by default; if unavailable, include a clearly labeled plain diff/code block and note why)
6. **Expected Impact for End-Users**
7. **Validation**
8. **Issues, Limitations, and Mitigations**