📦 deps(thirdparty): update snapshots

outfitter-agents/plugins/outfitter/templates/slash-commands/simple.md

@@ -0,0 +1,17 @@
+---
+description: [YOUR_DESCRIPTION] (e.g., "Review code for best practices and potential issues")
+---
+
+# [YOUR_COMMAND_NAME]
+
+[YOUR_PROMPT_INSTRUCTIONS]
+
+Example:
+Review the following code for:
+- Code quality and readability
+- Potential bugs or edge cases
+- Performance considerations
+- Security concerns
+- Test coverage
+
+Provide specific suggestions with code examples where applicable.

outfitter-agents/plugins/outfitter/templates/slash-commands/with-args.md

@@ -0,0 +1,38 @@
+---
+description: [YOUR_DESCRIPTION] (e.g., "Fix a specific issue by number")
+argument-hint: [YOUR_ARG_HINT] (e.g., "<issue-number>" or "<file1> <file2>")
+---
+
+# [YOUR_COMMAND_NAME]
+
+[YOUR_PROMPT_WITH_ARGUMENTS]
+
+## Examples:
+
+### Using $ARGUMENTS (all arguments as single string)
+
+Fix issues: $ARGUMENTS
+
+# Usage: /fix-issues 123 456 789
+
+# $ARGUMENTS = "123 456 789"
+
+### Using $1, $2, $3 (individual arguments)
+
+Review PR #$1 with priority $2 and assign to $3
+
+# Usage: /review-pr 456 high alice
+
+# $1="456", $2="high", $3="alice"
+
+### Combining arguments with file references
+
+Compare @$1 with @$2 and summarize differences
+
+# Usage: /compare src/old.ts src/new.ts
+
+# Will read both files and compare them
+
+## Your implementation:
+
+[REPLACE WITH YOUR COMMAND LOGIC]

outfitter-agents/plugins/outfitter/templates/slash-commands/with-bash.md

@@ -0,0 +1,37 @@
+---
+description: [YOUR_DESCRIPTION] (e.g., "Create a git commit from staged changes")
+allowed-tools: [YOUR_ALLOWED_TOOLS] (e.g., "Bash(git *)")
+---
+
+# [YOUR_COMMAND_NAME]
+
+## Context
+
+Current branch: !`git branch --show-current`
+
+Recent commits: !`git log --oneline -5`
+
+[YOUR_BASH_COMMANDS]
+Examples:
+- Git diff: !`git diff --staged`
+- Git status: !`git status`
+- File listing: !`ls -la src/`
+- Test results: !`bun test`
+- Environment info: !`node --version`
+
+## Task
+
+[YOUR_INSTRUCTIONS_USING_THE_BASH_OUTPUT_ABOVE]
+
+Example:
+Based on the staged changes shown above, create a single commit with:
+1. Clear, concise commit message (max 50 chars)
+2. Detailed body explaining the changes
+3. Reference any related issues
+
+## Notes
+
+- The `!` prefix executes bash commands before the prompt runs
+- Output is captured and included in the prompt context
+- Commands producing >15k chars are truncated (adjust with SLASH_COMMAND_TOOL_CHAR_BUDGET)
+- Use allowed-tools to restrict which tools Claude can use

outfitter-agents/plugins/outfitter/templates/slash-commands/with-files.md

@@ -0,0 +1,49 @@
+---
+description: [YOUR_DESCRIPTION] (e.g., "Analyze and explain a specific file")
+argument-hint: [YOUR_ARG_HINT] (e.g., "<file-path>")
+---
+
+# [YOUR_COMMAND_NAME]
+
+## File Contents
+
+**File**: @$1
+
+[ADDITIONAL_FILE_REFERENCES]
+Examples:
+- Single file: @src/utils/helpers.ts
+- Multiple files: @$1 and @$2
+- With arguments: @$1 for file path from user
+
+## Analysis
+
+[YOUR_INSTRUCTIONS_FOR_ANALYZING_THE_FILE_CONTENTS]
+
+Example:
+Provide a detailed explanation of:
+1. **Purpose**: What is this file responsible for?
+2. **Key Components**: Main functions, classes, and exports
+3. **Dependencies**: External libraries and internal imports
+4. **Architecture**: How does it fit in the larger system?
+5. **Potential Issues**: Bugs, performance concerns, or technical debt
+6. **Improvements**: Specific refactoring suggestions
+
+## Usage Examples
+
+```bash
+# Analyze a single file
+/analyze src/utils/helpers.ts
+
+# Compare two files
+/compare src/v1/api.ts src/v2/api.ts
+
+# Document a file
+/document src/components/Button.tsx
+```
+
+## Notes
+
+- The `@` prefix includes file contents in the prompt
+- Files are read at command execution time
+- Combine with arguments: `@$1` for dynamic file paths
+- Works with relative paths from project root