analyze-only
01Command Claude CodeCursor
DO NOT CHANGE ANY CODE. Perform analysis and provide recommendations only.
Command Claude CodeCursor
DO NOT CHANGE ANY CODE. Perform analysis and provide recommendations only.
Command Claude CodeCursor
Run make check-all and fix all issues including failed tests.
Command Claude CodeCursor
Analyze uncommitted changes, create a branch if needed, and commit with a well-structured message.
Command Claude CodeCursor
Command "create-backend-tests" from codeready-toolchain/tarsy, covering writing tests for go backend, running tests, from project root, direct go commands and critical rules.
Command Claude CodeCursor
You'll typically use this after implementing new dashboard functionality. Create tests for the complex logic you just added.
Command Claude CodeCursor
Command "create-python-tests" from codeready-toolchain/tarsy, covering writing tests for python llm service, running tests, from project root, from llm-service/ directory and critical rules.
Command Claude CodeCursor
You are in design mode. Generate two documents and then walk through the questions together.
Command Claude CodeCursor
Extract non-obvious learnings from this session into scoped AGENTS.md files.
Command Claude CodeCursor
Run make lint and fix all identified issues.
Command Claude CodeCursor
The user's message contains a Pull Request review comment that needs to be addressed.
Command Claude CodeCursor
Move an implemented proposal from docs/proposals/ to docs/adr/ as a numbered Architecture Decision Record.
Command Claude CodeCursor
Perform thorough internet research to gather the most current and comprehensive information.
Command Claude CodeCursor
Remove AI code slop from the current branch vs default branch.
Command Claude CodeCursor
You are in sketch mode. The feature or idea is not yet well-defined enough for a detailed design. Your job is to produce a high-level technical sketch and a questions document, then walk through the questions one at a time to form the sketch. Do not attempt detailed architecture, implementation plans, or interface…
Command Claude CodeCursor
Update relevant documentation to reflect recent code changes.
Command Claude CodeCursor
Carefully and systematically review the provided design document to verify it is consistent, aligned with the current codebase, and free of meaningful gaps. Fix everything you can, then ask about the rest.
Skill Cursor
Review and clean up auto-generated database migration files after running make migrate-create. Identifies and removes unrelated Atlas schema drift such as dropped partial indexes, no-op index recreations, and other operations not related to the intended migration. Use when creating database migrations, running make…
Skill Cursor
Context usage patterns for Go including cancellation, timeouts, deadlines, and database transactions. Use when handling HTTP requests, database operations, or implementing cancellation and timeout logic.
Skill Cursor
Error handling patterns for Go including error wrapping, custom errors, sentinel errors, and error checking best practices. Use when implementing error handling, defining error types, or working with error flows.
Skill Cursor
Modern Go testing patterns including table-driven tests, subtests, test organization, and best practices. Use when writing or refactoring tests, implementing test coverage, or when the user asks about Go testing approaches.
Skill Cursor
Prefer typed constants and named types over magic strings/numbers in Go. Use when writing function signatures, struct fields, switch statements, or passing enum-like values.
Skill Cursor
Behavioral guidelines to reduce common LLM coding mistakes (think before coding, simplicity, surgical changes, goal-driven execution). Use when implementing features, fixing bugs, refactoring, reviewing code, or any other coding task.
Skill Claude CodeCursor
Apply modern Go syntax based on this repository's Go version. Use when writing, editing, or reviewing Go code, or when the user asks for modern Go guidelines.
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: