I got tired of adding the same set of commands to each repo, so created a marketplace for the stuff I use on every project. More on this later …
Give it a try and let me know what you think!
I got tired of adding the same set of commands to each repo, so created a marketplace for the stuff I use on every project. More on this later …
Give it a try and let me know what you think!
implement-tests test commandIt is useful at times to have a separate test and implement commands:
## Payment Processing
The system supports credit card payments via Stripe. Users can save multiple
payment methods and set a default. All transactions are logged for audit
purposes.
/plan payment-processing
Inspect plan.
/implement-tests
Inspect tests.
Run tests to verify they fail (red phase)
Implement the code:
/implement
Example of using this plugin to generate KiCad library parts:
Added/execute commandFinds and executes inline instructions or pseudo code marked with special tags in your code or documentation. This enables surgical, targeted changes without needing full documentation rewrites.
The command looks for instruction markers in these formats:
@CLAUDE: <instruction> - Single line instruction
@CLAUDE-START / @CLAUDE-END - Multi-line instruction blocks
In code comments: // @CLAUDE:, # @CLAUDE:, /* @CLAUDE: */, <!-- @CLAUDE: -->
In markdown: Lines starting with > @CLAUDE: or within code blocks
How it works:
Searches uncommitted changes (from git diff) for instruction markers
Executes each instruction or pseudo code as described
Removes the marker tags after successful completion
Updates any uncommitted plan files to reflect what was done
Example usage:
Add an instruction marker in your code:
# @CLAUDE: Add error handling for network timeouts
def fetch_data(url):
response = requests.get(url)
return response.json()
Run /execute to implement the instruction and remove the marker.
Use this command for quick, focused changes like adding error handling, refactoring specific functions, or implementing small improvements.
added/release[version]Automates the release process by:
Converting the [Unreleased] section in CHANGELOG.md to a versioned release with the current date
Updating version numbers in all manifest files (e.g., .claude-plugin/plugin.json)
Creating a git tag for the release
Usage:
/release - Auto-increments the patch version (e.g., 1.0.6 → 1.0.7)
/release 2.0.0 - Uses the specified version number
The command does not automatically commit or push changes, allowing you to review before finalizing.
One thing that is a little messy is we are typically on a branch in repos to make changes (push to main is often disabled), so this may have limited utility in those scenarios. Perhaps we should remove the tag part, assuming that will need to happen separately.