Quality Gates Configuration

## Mandatory Pre-Commit Checks
 
**All of the following checks must pass before any commit is allowed:**
 
1. **Linter Check**: `npm run lint` must produce zero warnings and zero errors
2. **Test Check**: `npm test` must pass completely
3. **Format Check**: `npm run format:check` must pass
4. **Type Check**: `npm run type-check` must pass
 
**Important**: If any check fails, it must be fixed before committing. Never use `--no-verify` to bypass checks.

## Absolute Prohibition List
 
**The following behaviors are never allowed, with no exceptions:**
 
### Code Quality
- Never commit code that fails tests
- Never use TODO/FIXME/HACK in final code
- Never skip error handling
- Never swallow exceptions (empty catch blocks)
- Never use magic numbers (define constants instead)
 
### Type Safety
- Never use the any type (use unknown + type guards)
- Never use @ts-ignore (fix the root issue)
- Never disable ESLint rules (eslint-disable)
 
### Security
- Never hardcode secrets, passwords, or tokens
- Never include sensitive data in code
- Never trust unvalidated user input

## Quality Gates
 
**Important: The following rules are absolute minimums with no exceptions whatsoever**
 
### Mandatory Pre-Commit Checks (All Must Pass)
 
Before committing any code, ensure all of the following checks pass:
 
1. **Linter Check**
   - Command: `npm run lint`
   - Standard: zero warnings, zero errors
   - Never use `eslint-disable` to bypass rules
 
2. **Test Check**
   - Command: `npm test`
   - Standard: all tests must pass
   - New code must have corresponding tests
 
3. **Format Check**
   - Command: `npm run format:check`
   - Standard: all files are correctly formatted
 
4. **Type Check** (TypeScript projects)
   - Command: `npm run type-check`
   - Standard: no errors under TypeScript strict mode
 
### Absolute Prohibition List (Never Allowed)
 
The following behaviors are prohibited under any circumstances:
 
**Code Quality**
- Never commit code that fails tests
- Never use TODO/FIXME in final code
- Never skip error handling
- Never swallow exceptions (empty catch blocks)
- Never use magic numbers
 
**Type Safety**
- Never use the any type (use unknown instead)
- Never use @ts-ignore
- Never disable ESLint rules
 
**Security**
- Never hardcode secrets/credentials
- Never output sensitive data in logs
- Never skip input validation
 
### Handling Violations
 
If code is found to violate any of the above gates:
1. Must fix immediately
2. Cannot be bypassed in any way
3. Cannot be excepted as a "temporary solution"

## Consequences of Gate Violations
 
If code output violates any of the above gates:
- The code will be considered **unacceptable** and must be rewritten
- No "special circumstances" or "temporary solution" exceptions are accepted
- "Commit now, fix later" is not accepted

## Pre-Submission Self-Check
 
Before outputting final code, confirm each item:
 
- [ ] Did I use the any type? → If yes, change to unknown
- [ ] Are there empty catch blocks? → If yes, add error handling
- [ ] Are there TODO/FIXME comments? → If yes, complete them now
- [ ] Are there hardcoded configurations? → If yes, move to environment variables
- [ ] Did I run the linter? → If not, run it now
 
**Only output the code after all items are confirmed**

## Development Process vs. Commit Standards
 
### During Development (can be relaxed)
- May use console.log for debugging
- May temporarily skip some tests
- May use simplified implementations
 
### At Commit Time (must be strict)
- Must remove all debug code
- Must ensure all tests pass
- Must be production-ready code