Slash Command1.1k estrellas del repoactualizado 3mo ago

todo

The todo slash command automatically inserts TODO comments into code files with language-appropriate syntax. It detects priority levels from prefixes (exclamation mark for HIGH, question mark for DISCUSS) and formats comments correctly for JavaScript, Python, HTML, CSS, Shell, and other languages, positioning them logically near related code or at block starts.

Ver fuente Repositorio: claude-code-engineering

Instalar en Claude Code

Copiar

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/huangjia2019/claude-code-engineering/HEAD/05-Commands/projects/01-basic-commands/.claude/commands/todo.md -o ~/.claude/commands/todo.md

Después abre una sesión nueva de Claude Code; el slash command carga automáticamente.

Definición

todo.md

Add a TODO comment based on: $ARGUMENTS

## Priority Detection

- `!` at start → HIGH priority: `// TODO [HIGH]: message`
- `?` at start → DISCUSS: `// TODO [DISCUSS]: message`
- No marker → Normal: `// TODO: message`

## Comment Format by Language

Detect the file type and use appropriate comment syntax:

- JavaScript/TypeScript: `// TODO: message`
- Python: `# TODO: message`
- HTML: `<!-- TODO: message -->`
- CSS: `/* TODO: message */`
- Shell: `# TODO: message`

## Steps

1. Identify the file context (currently open or recently edited)
2. Parse the message and detect priority
3. Format the TODO comment appropriately
4. Add at a logical location:
   - Near related code if context is clear
   - At the top of the function/block otherwise
5. Confirm the addition

## Examples

Input: `/todo fix null check`
Output: `// TODO: fix null check`

Input: `/todo ! critical security fix`
Output: `// TODO [HIGH]: critical security fix`

Input: `/todo ? should we use async here`
Output: `// TODO [DISCUSS]: should we use async here`

## Output

Confirm briefly:
```
✓ Added TODO at [file]:[line]
```

Del mismo repositorio

analyzeSlash Command

Deep analysis of code against project standards

api-conventionsSkill

API design patterns and conventions for this project. Covers RESTful URL naming, response format standards, error handling, and authentication requirements. Use when writing or reviewing API endpoints, designing new APIs, or making decisions about request/response formats.

api-doc-generatorSubagent

Generate comprehensive API documentation by scanning Express route files.

api-documentingSkill

Generate API documentation from code. Use when the user wants to document APIs, create API reference, generate endpoint documentation, or needs help with OpenAPI/Swagger specs.

api-explorerSubagent

Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.

api-generatingSkill

Generate API endpoint documentation from Express route files. Use when the user asks to generate, update, or review API docs for Express.js routes.

auth-explorerSubagent

Explore and analyze authentication-related code. Use when investigating auth flows, session management, or security.

bug-analyzerSubagent

Analyze root cause of bugs after location is identified. Second step in bug investigation.