ctx-update
25Command Claude Code
Update existing project context to match current state.
Command Claude Code
Update existing project context to match current state.
Command Claude Code
Verify context accuracy against current project state.
Command Claude Code
Review code changes against project standards.
Command Claude Code
Debug and fix failing tests.
Agent Claude CodeCursor
When to use this subagent. Be specific so the AI delegates correctly. Include 'Use proactively when...' if it should be suggested often.
Agent Claude CodeCursor
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use when the user asks for a review or after writing or modifying code.
Agent Claude CodeCursor
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when the user hits an error, failing test, or bug.
Command Claude CodeCursor
Describe what this command should do. When the user runs /command-name, this content is sent as the prompt.
Command Claude CodeCursor
Write tests for newly implemented or currently untested code. Aim for meaningful coverage of the implementation. Do not run the full test suite—only the new tests you add.
Command Claude CodeCursor
Review the code I’m working on (current file or selection, or recent changes if nothing is selected).
Command Claude CodeCursor
Guide the user through systematic debugging step by step. Teach the process; don’t just fix the bug.
Command Claude CodeCursor
Look at the recent git changes (e.g. git diff or last commit) and explain what changed and why it matters.
Command Claude CodeCursor
Produce a short implementation brief so the next step (or the user) can implement without re-explaining.
Command Claude CodeCursor
The user wants to go deeper on a topic. Create a curated reading list they can use later. Place all reading lists in /Developer/personal/Obsidian/Personal/Knowledge/Reading\ Lists/ (create if not pre-existing) and title the list appropriately.
Command Claude CodeCursor
The operational phase of this session is complete. You are now in the role of Meta-Architect and Guardian of the Config (rules, commands, agents, and skills).
Cursor rule Cursor
One-line description of what this rule does (shown in rule picker).
Cursor rule Cursor
Commenting: explain WHY not WHAT. Readability over cleverness. When to comment vs skip.
Cursor rule Cursor
Complete entire task chains; if task A reveals issue B, fix both before marking done. No partial completion.
Cursor rule Cursor
Reply in a concise style; avoid repetition and filler. Prefer short, actionable answers.
Cursor rule Cursor
Before suggesting or running destructive or high-impact operations, state the risk and ask for explicit confirmation.
Cursor rule Cursor
Use Read/Write/StrReplace for file content; use bash only for system commands (git, npm, etc.). Don't use sed/awk/cat for editing.
Cursor rule Cursor
Git: manual only (no auto-commit/push). UI: ask before implementing. Docs: check before using libraries. Apply every request.
Cursor rule Cursor
Git workflow: conventional commits, branch naming, delta, allowed vs approval-required operations.
Cursor rule Cursor
For multi-step or ambiguous tasks, propose a short todo list (or confirm steps) and get approval before executing.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: