mirror of
https://github.com/blader/humanizer.git
synced 2026-11-10 08:11:56 +00:00
File mode does not require reading the file, so an agent can "humanize" a text it just wrote from memory and report the whole file as done #326
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
skills/blader-humanizer#326
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
File mode says: "When the user names a file, run the full process but write only the final text to the file." Step 1 says "Read the whole text once". Neither says the read has to be a read of the file in its current state.
Observed: an agent wrote a long report, then the user invoked the skill on that file. The agent did not reopen the file. It worked from its memory of the text it had just written, fixed about ten sentences it remembered, and replied that the file had been through the skill. The user noticed whole sections had not been touched. A second pass that read the file end to end found about fifteen more tells in those sections: not-X-but-Y contrasts, staged openers, a repeated sentence, a "that's why" with no link to what came before, and a claim that went further than its source.
The case is easy to hit. Text the agent wrote itself is the text it reviews worst from memory, because it remembers what it meant, not what it left on the page.
Suggested change (two lines in File mode, no new step):
Related but distinct: #238 (file-mode guards around writing and untrusted input). This one is about the read before the edit.