mirror of
https://github.com/davila7/claude-code-templates.git
synced 2026-09-19 01:30:23 +08:00
054c0e56e9
Removed the deprecated 'model: sonnet' field from command frontmatter to fix compatibility issues with Claude Code. Commands will now inherit the model from the active conversation instead of using a hardcoded deprecated model identifier. Changes: - Removed 'model: sonnet' from 142 command files across all categories - Commands now use default model inheritance behavior - Preserved 'model: claude-sonnet-4-5-20250929' in gemini-review.md (valid model) - 67 commands without model field remain unchanged This resolves the "model: sonnet not found" error reported in GitHub issues and aligns with Claude Code's recommended practice of letting commands inherit the conversation model. Affected categories: - Database/Supabase commands (8 files) - Documentation commands (8 files) - Deployment commands (11 files) - Setup commands (14 files) - Performance commands (8 files) - Team commands (14 files) - Security commands (6 files) - NextJS/Vercel commands (10 files) - Sync commands (14 files) - And more across other categories 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
3.0 KiB
3.0 KiB
allowed-tools: Read, Write, Edit
argument-hint: [action] [task-description] | add | complete | remove | list
description: Manage project todos in todos.md file
Project Todo Manager
Manage todos in a todos.md file at the root of your current project directory: $ARGUMENTS
Usage Examples:
/user:todo add "Fix navigation bug"/user:todo add "Fix navigation bug" [date/time/"tomorrow"/"next week"]an optional 2nd parameter to set a due date/user:todo complete 1/user:todo remove 2/user:todo list/user:todo undo 1
Instructions:
You are a todo manager for the current project. When this command is invoked:
- Determine the project root by looking for common indicators (.git, package.json, etc.)
- Locate or create
todos.mdin the project root - Parse the command arguments to determine the action:
add "task description"- Add a new todoadd "task description" [tomorrow|next week|4 days|June 9|12-24-2025|etc...]- Add a new todo with the provided due datedue N [tomorrow|next week|4 days|June 9|12-24-2025|etc...]- Mark todo N with the due date providedcomplete N- Mark todo N as completed and move from the ##Active list to the ##Completed listremove N- Remove todo N entirelyundo N- Mark completed todo N as incompletelist [N]or no args - Show all (or N number of) todos in a user-friendly format, with each todo numbered for referencepast due- Show all of the tasks which are past due and still activenext- Shows the next active task in the list, this should respect Due dates, if there are any. If not, just show the first todo in the Active list
Todo Format:
Use this markdown format in todos.md:
# Project Todos
## Active
- [ ] Task description here | Due: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified)
- [ ] Another task
## Completed
- [x] Finished task | Done: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified)
- [x] Another completed task | Due: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified) | Done: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified)
Behavior:
- Number todos when displaying (1, 2, 3...)
- Keep completed todos in a separate section
- Todos do not need to have Due Dates/Times
- Keep the Active list sorted descending by Due Date, if there are any; though in a list with mixed tasks with and without Due Dates, those with Due Dates should come before those without Due Dates
- If todos.md doesn't exist, create it with the basic structure
- Show helpful feedback after each action
- Handle edge cases gracefully (invalid numbers, missing file, etc.)
- All provided dates/times should be saved/formatted in a standardized format of MM/DD/YYYY (or DD/MM/YYYY depending on locale), unless the user specifies a different format
- Times should not be included in the due date format unless requested (
due N in 2 hoursshould be MM/DD/YYYY @ [+ 2 hours from now])
Always be concise and helpful in your responses.