Clarify lazy as less work for the same result#532
Open
mitzracing wants to merge 1 commit into
Open
Conversation
2471909 to
d8ad387
Compare
d8ad387 to
0548ed5
Compare
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Clarifies Ponytail's high-salience wording so "lazy" means less work for the same correct result, not less understanding.
This does not add a new rule. The repo already says the ladder runs after understanding the problem, that bug fixes should address the root cause, and that validation/security/accessibility/checks are not optional. This PR moves that standard into the first sentence and the skill description so the core promise is harder to misread as "do less than the task requires."
Why
The failure mode this targets is over-laziness: an agent satisfying the style by giving a cheaper/shallow answer instead of finding the easiest path that still reaches the requested result. Ponytail should cut unnecessary work, not the result.
Example failure mode: an agent optimizes for a cheap answer and returns less than the task asked for, instead of finding the simplest path that still gets the requested outcome.
This is a surface clarification of the same comprehension-first/root-cause philosophy already documented in the repo's #245/#217 writeup; it does not add a new rule.
Validation
node scripts/check-rule-copies.jsnode --test tests/openclaw-skills.test.jsnode --check hooks/ponytail-instructions.jspython3 -m py_compile __init__.pynode --test tests/hooks.test.jsnpm testwas run locally; the only remaining failure is the existing environment dependencytests/correctness.test.jsCSV pandas case because this container lackspandas(ModuleNotFoundError: No module named 'pandas').