dev-mcp-tools: Command for Claude Code

QCHECKF - Function-Focused Review

When user types "qcheckf", execute this workflow as a SKEPTICAL senior software engineer:

Focus: Writing Functions Best Practices Only

For every MAJOR function added or edited (skip minor changes):

Function Quality Checklist (CLAUDE.md)

1. Readability: Can you read the function and HONESTLY easily follow what it's doing? If yes, stop here.
2. Complexity: Does the function have very high cyclomatic complexity? (number of independent paths, nesting levels)
3. Data Structures: Are there any common data structures and algorithms that would make this function much easier to follow and more robust? (parsers, trees, stacks/queues, etc.)
4. Parameters: Are there any unused parameters in the function?
5. Type Casts: Are there any unnecessary type casts that can be moved to function arguments?
6. Testability: Is the function easily testable without mocking core features (sql queries, redis, etc.)? If not, can it be tested via integration test?
7. Dependencies: Does it have any hidden untested dependencies or values that can be factored out into arguments? (Only care about non-trivial dependencies that can actually change)
8. Naming: Brainstorm 3 better function names and see if current name is the best, consistent with rest of codebase.

Refactoring Rules

❌ SHOULD NOT refactor out a separate function unless:

• The refactored function is used in more than one place
• The refactored function is easily unit testable while the original is not AND you can't test it any other way
• The original function is extremely hard to follow and you resort to putting comments everywhere

Response Template

🔍 **QCHECKF - Function Review**

**Functions Analyzed:**

**Function**: `functionName` in `file.ts:line`
1. **Readability**: ✅/❌ [Can honestly easily follow? If yes, stop here]
2. **Complexity**: ✅/❌ [Cyclomatic complexity assessment] 
3. **Data Structures**: ✅/❌ [Could benefit from trees/parsers/etc?]
4. **Parameters**: ✅/❌ [Any unused parameters?]
5. **Type Casts**: ✅/❌ [Unnecessary casts to move to args?]
6. **Testability**: ✅/❌ [Easy to test without heavy mocking?]
7. **Dependencies**: ✅/❌ [Hidden dependencies to factor out?]
8. **Naming**: ✅/❌ [Better alternatives: name1, name2, name3]

**Refactoring Assessment:**
- Should extract function? ✅/❌ [Reason if yes]
- Reuse potential: [none/low/medium/high]
- Testing benefits: [none/some/significant]

**Recommendations:**
[Specific suggestions for improvement]

**Function Status:** ✅ Solid / ⚠️ Needs tweaks / ❌ Major issues