diff options
| -rw-r--r-- | prompts/commands/commit-and-push-to-git.md | 3 | ||||
| -rw-r--r-- | prompts/commands/create-command.md | 38 | ||||
| -rw-r--r-- | prompts/commands/delete-command.md | 34 | ||||
| -rw-r--r-- | prompts/commands/increment-version-and-push.md | 3 | ||||
| -rw-r--r-- | prompts/commands/update-command.md | 40 |
5 files changed, 118 insertions, 0 deletions
diff --git a/prompts/commands/commit-and-push-to-git.md b/prompts/commands/commit-and-push-to-git.md new file mode 100644 index 0000000..42132bd --- /dev/null +++ b/prompts/commands/commit-and-push-to-git.md @@ -0,0 +1,3 @@ +# Commit and push to git + +Commit and push to git all changes you made. diff --git a/prompts/commands/create-command.md b/prompts/commands/create-command.md new file mode 100644 index 0000000..26a8f38 --- /dev/null +++ b/prompts/commands/create-command.md @@ -0,0 +1,38 @@ +# /create-command + +**Description:** Create a new slash command by inferring its purpose and prompt from the command name. The command will analyze the name, generate an appropriate description and prompt, then save it to ~/Notes/Prompts/commands/. + +**Parameters:** +- command_name: The name of the new command to create (e.g., "review-code", "explain-error", "optimize-function") + +**Example usage:** +- `/create-command review-code` +- `/create-command explain-error` + +--- + +## Prompt + +I'll create a new slash command called `/{{command_name}}`. Here's my process: + +1. **Analyze the command name** "{{command_name}}" to infer its purpose: + - Break down the name into meaningful parts + - Determine the likely intent and use case + - Identify what parameters it might need + +2. **Generate the command structure**: + - Create an appropriate description based on the inferred purpose + - Define relevant parameters if applicable + - Write a detailed prompt that accomplishes the command's goal + +3. **Show you a preview** of the generated command and ask if you want to: + - Use it as-is + - Modify the description + - Adjust the parameters + - Refine the prompt text + +4. **Save the command** to `~/Notes/Prompts/commands/{{command_name}}.md` + +5. **Confirm** the command is ready to use as `/{{command_name}}` + +Let me start by analyzing the command name and generating the initial version... diff --git a/prompts/commands/delete-command.md b/prompts/commands/delete-command.md new file mode 100644 index 0000000..98c365c --- /dev/null +++ b/prompts/commands/delete-command.md @@ -0,0 +1,34 @@ +# /delete-command + +**Description:** Delete an existing slash command by removing its definition file from ~/Notes/Prompts/commands/. This command will confirm before deletion and show you which commands are available to delete. + +**Parameters:** +- command_name: The name of the command to delete (e.g., "testing", "review-code") + +**Example usage:** +- `/delete-command testing` +- `/delete-command review-code` + +--- + +## Prompt + +I'll help you delete the `/{{command_name}}` command. Here's what I'll do: + +1. **Verify the command exists**: + - Check if `~/Notes/Prompts/commands/{{command_name}}.md` exists + - Show you the command's current description + +2. **Confirm deletion**: + - Display the command file that will be deleted + - Ask for your confirmation before proceeding + +3. **Delete the command**: + - Remove the file from `~/Notes/Prompts/commands/` + - Confirm successful deletion + +4. **Clean up** (if applicable): + - Note: The command will no longer be available after deletion + - You can always recreate it later using `/create-command` if needed + +Let me check if the command exists and show you what will be deleted... diff --git a/prompts/commands/increment-version-and-push.md b/prompts/commands/increment-version-and-push.md new file mode 100644 index 0000000..015038b --- /dev/null +++ b/prompts/commands/increment-version-and-push.md @@ -0,0 +1,3 @@ +# Increment version and push + +Increment the version of the project, tag it in git, commit, and push. For Go-based projects, look for the internal/version.go file. For bug fixes, increment only the minor version. We are using semantic versioning, e.g., x.y.z, where z is the minor version. For new features, increment y. Never increment x (the major version) unless specified. diff --git a/prompts/commands/update-command.md b/prompts/commands/update-command.md new file mode 100644 index 0000000..a74cecc --- /dev/null +++ b/prompts/commands/update-command.md @@ -0,0 +1,40 @@ +# /update-command + +**Description:** Guide me step-by-step to update an existing slash command in ~/Notes/Prompts/commands/. Help me modify the description, parameters, prompt text, or any other aspect of the command. + +**Parameters:** +- command_name: The name of the existing command to update (e.g., "create-command" for /create-command) + +**Example usage:** +- `/update-command create-command` +- `/update-command review-code` + +--- + +## Prompt + +I need to update an existing slash command. Please follow these steps: + +1. **Read the existing command file** from `~/Notes/Prompts/commands/{{command_name}}.md` + - If the file doesn't exist, inform me and list available commands in that directory + +2. **Show me the current content** of the command in a clear, organized format + +3. **Ask me what I want to update** using the AskUserQuestion tool: + - Description + - Parameters (add, remove, or modify) + - Prompt text/content + - All of the above + +4. **Guide me through the updates** interactively: + - For description: Ask for the new description + - For parameters: Show current parameters and ask what to add/remove/modify + - For prompt text: Ask for the new prompt content or specific sections to change + +5. **Show me a preview** of the updated command before saving + +6. **Save the updated command** back to `~/Notes/Prompts/commands/{{command_name}}.md` + +7. **Confirm** the update was successful and summarize what changed + +Be helpful and thorough - make sure I understand each change and why it improves the command. |