[EPIC] TypeScript Migration Foundation

[ballidev]

Epic: TypeScript Migration Foundation

This epic tracks the foundational work needed to migrate cc-commands from Bash to TypeScript using oclif.

Scope

• Setup oclif project structure
• Configure build system with Vitest
• Setup testing framework
• Create base interfaces and types
• Establish coding standards

Success Criteria

• oclif project initialized with TypeScript
• Vitest testing framework configured
• ESLint and Prettier configured
• Base interfaces defined
• CI/CD pipeline updated for TypeScript

Plan Document

See: TYPESCRIPT_MIGRATION_PLAN.md

[ballidev]

Additional ESLint Rule Ideas

Prevent eslint-disable comments in source code

We should consider adding a custom ESLint rule to completely ban eslint-disable comments in the src/ directory. This would enforce our principle that issues should be fixed, not ignored.

Current situation:

• We've eliminated all eslint-disable comments from our source code ✅
• We have @typescript-eslint/no-explicit-any set to "error" ✅
• We've added eslint-plugin-eslint-comments for better comment management ✅

Attempted implementation:
We tried using no-restricted-syntax with various AST selectors but couldn't get the right syntax to match eslint-disable comments. The eslint-comments plugin doesn't have a rule to completely ban disable comments.

Future enhancement:
Create a custom ESLint rule that:

1. Detects any comment containing eslint-disable
2. Reports it as an error in src/ directory
3. Allows it in test/ directory (where it might be needed for testing edge cases)

This would ensure developers can't take shortcuts by disabling rules instead of fixing the underlying issues.

Reference: The discussion about this came up when we noticed developers (including AI assistants!) tend to use any types as a lazy shortcut. The no-explicit-any rule helps, but preventing eslint-disable would make it impossible to bypass.