Improve descriptions and hints for set commands - #10
Merged
Merged
Conversation
commit: |
gskril
changed the title
ens set commands
gskril
changed the title
ens set commandsThis reverts commit 8e3fb99.
gskril
changed the title
gskril
changed the title
Member
Author
|
No functional changes, just updating descriptions and hints to look cleaner for humans and be clearer for agents |
…tadata # Conflicts: # src/commands/set.ts
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
1 participant
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
ens set address,text,contenthash, andbatchsubcommandsWhy
The existing descriptions mixed terse command-list labels with detailed operational guidance. This made the parent
ens set --helplisting noisy and duplicated information that Incur is designed to expose through hints and examples.Impact
The
ens setcommand list is now concise, while each subcommand's detailed help and generated skill documentation retain consumer-facing resolver behavior and concrete usage examples. Command execution and batch validation behavior are unchanged.Validation
bun run typecheckbun test --pass-with-no-tests(repository currently contains no test files)bun run buildgit diff --check