Self documenting code in Typescript

typescript
Avoid unnecessary explanatory comments for code that is self-documenting. Comments should only be used when they add context that the code itself cannot convey.
Bad:
```typescript
// Use the test-specific directory path
testDir = join(BASE_DIR, testCase.identifier)
```

Install this rule for wispbit

Add this rule to wispbit and it will run when you open a pull request

Install this rule for Coderabbit

Copy the configuration below and add it to your repository as .coderabbit.yml in your project root.

reviews:
  path_instructions:
    - path: "*.ts,*.tsx"
      instructions: |
                
        Avoid unnecessary explanatory comments for code that is self-documenting. Comments should only be used when they add context that the code itself cannot convey.
        
        Bad:
        
        ```typescript
        // Use the test-specific directory path
        testDir = join(BASE_DIR, testCase.identifier)
        ```
        
        Good:
        
        ```typescript
        testDir = join(BASE_DIR, testCase.identifier)
        ```

Install this rule for Greptile

Greptile rules can be added through the web interface. Please see this documentation for details on how to add custom rules and context.

Avoid unnecessary explanatory comments for code that is self-documenting. Comments should only be used when they add context that the code itself cannot convey.
Bad:
```typescript
// Use the test-specific directory path
testDir = join(BASE_DIR, testCase.identifier)
```
Good:
```typescript
testDir = join(BASE_DIR, testCase.identifier)
```

File Path Patterns:

*.ts
*.tsx

Install this rule for GitHub Copilot

Copilot instructions can be added through the interface. See the documentation for details on how to create coding guidelines.

Avoid unnecessary explanatory comments for code that is self-documenting. Comments should only be used when they add context that the code itself cannot convey.
Bad:
```typescript
// Use the test-specific directory path
testDir = join(BASE_DIR, testCase.identifier)
```
Good:
```typescript
testDir = join(BASE_DIR, testCase.identifier)
```

File Path Patterns:

*.ts
*.tsx

Install this rule for Graphite Diamond

Diamond custom rules can be added through the interface. See the documentation for details on how to create custom rules.

Avoid unnecessary explanatory comments for code that is self-documenting. Comments should only be used when they add context that the code itself cannot convey.
Bad:
```typescript
// Use the test-specific directory path
testDir = join(BASE_DIR, testCase.identifier)
```
Good:
```typescript
testDir = join(BASE_DIR, testCase.identifier)
```

File Path Patterns:

*.ts
*.tsx

Use with Cline

Copy the rule below and ask Cline to review your code using this rule

Avoid unnecessary explanatory comments for code that is self-documenting. Comments should only be used when they add context that the code itself cannot convey.
Bad:
```typescript
// Use the test-specific directory path
testDir = join(BASE_DIR, testCase.identifier)
```
Good:
```typescript
testDir = join(BASE_DIR, testCase.identifier)
```

Use with OpenAI Codex

Copy the rule below and ask OpenAI Codex to review your code using this rule

Avoid unnecessary explanatory comments for code that is self-documenting. Comments should only be used when they add context that the code itself cannot convey.
Bad:
```typescript
// Use the test-specific directory path
testDir = join(BASE_DIR, testCase.identifier)
```
Good:
```typescript
testDir = join(BASE_DIR, testCase.identifier)
```

Use with Cursor

Copy the rule below and ask Cursor to review your code using this rule

Avoid unnecessary explanatory comments for code that is self-documenting. Comments should only be used when they add context that the code itself cannot convey.
Bad:
```typescript
// Use the test-specific directory path
testDir = join(BASE_DIR, testCase.identifier)
```
Good:
```typescript
testDir = join(BASE_DIR, testCase.identifier)
```

Use with Claude Code

Copy the rule below and ask Claude Code to review your code using this rule

Avoid unnecessary explanatory comments for code that is self-documenting. Comments should only be used when they add context that the code itself cannot convey.
Bad:
```typescript
// Use the test-specific directory path
testDir = join(BASE_DIR, testCase.identifier)
```
Good:
```typescript
testDir = join(BASE_DIR, testCase.identifier)
```

Install this rule for Windsurf

To set up rules for Windsurf Reviews, please see this documentation 

Avoid unnecessary explanatory comments for code that is self-documenting. Comments should only be used when they add context that the code itself cannot convey.
Bad:
```typescript
// Use the test-specific directory path
testDir = join(BASE_DIR, testCase.identifier)
```
Good:
```typescript
testDir = join(BASE_DIR, testCase.identifier)
```