feat: support $ARGUMENTS and positional argument substitution for prompts #3233
+87
−1
Conversation
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.
Issue #, if available: #3064
Description of changes:
This PR is addressing the issue in #3064, but with different syntax, i.e. instead of placeholder {{arg1}}, this will adopt the syntax $ARGUMENTS and $1, $2, $3, ...
This syntax is to fulfill the requirements for Spec Kit and OpenSpec, which are both claimed to support or partially support of Amazon Q CLI, but lacks of $ARGUMENTS prevent the full usage of these two popular Spec-Driven Development (SDD) tools.
Note
There is another PR available, which is also linked to #3064. Which take advantage of frontmatter for setting key-value substitution of prompts. I believe both PRs are good solutions to the original issue, and may be useful for different scenarios. I am OK to combine them as long as the final solution works with the Spect Kit and OpenSpec.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.