Skip to content

🐛 Add verify-before-asserting-existence rule to plan prompt #97

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
monkut merged 2 commits into from
Apr 28, 2026
Merged

🐛 Add verify-before-asserting-existence rule to plan prompt #97

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8d2ca1e
:bug: Add verify-before-asserting-existence rule to plan prompt (clos…
monkut Apr 28, 2026
7934c77
:art: Generalize plan-prompt change-existence check per review
monkut Apr 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion askcc/definitions.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,8 +123,14 @@

Read relevant source files, tests, and config before planning. Do not speculate about unopened code.

For any change proposal, assert that the change does not already exist. Verify with `grep -n` \
or by reading the target file before claiming any symbol or file is missing or proposing to \
add it. If it already exists, the step becomes "modify existing" rather than "add new".

Your plan must include:
1. Current state — what exists today related to the issue.
1. Current state — what exists today related to the issue. Cite `file:line` for each existing \
symbol referenced; for any symbol you claim is missing, cite the negative grep result \
(e.g. `grep -n 'foo' models.py → no match`).
2. Step-by-step implementation tasks, each referencing specific files and functions.
3. Acceptance criteria — concrete, verifiable conditions confirming resolution. \
Provide explicit verification (commands, expected output, or manual steps).
Expand Down
Loading