feat(commands): add file tag support for custom command prompts #271
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.
Background
hey @intellectronica! this is a great library, i've been using it in a couple of my projects. however, since this PR #247 about custom commands, i thought about something.
since many IDE/CLI tools have built-in directories for custom commands (not in the rules), i wonder if we can extend this feature so users can use prompt-file instead of only using prompt. i think when we try to add prompts in the TOML, commands that are really long can be hard to write. also, it cannot use markdown for more specific tasks.
so the ideas is to:
let me know your thoughts on these changes!
Summary
extend custom commands to support file tag syntax in prompt files, allowing commands to reference and include specific files using tag-based notation (e.g., prompt_file tags).
What's Changed
Screenshot