🛡️ Todo Paranoid - Block Forbidden Comments

Never commit embarrassing comments again! Todo Paranoid prevents you from accidentally committing sensitive comments like //PARANOID: use fake password while still allowing you to test your code locally.

🎯 What Does It Do?

Todo Paranoid tracks two types of comments in your code:

🚫 BLOCKING Comments (Prevent Commits)

//PARANOID: temporary test code
//NOCOMMIT: remove this line
You can save and test these files locally ✅
Cannot commit them to Git ❌

📝 TRACKING Comments (Organizational Only)

//TODO: optimize this function
//FIXME: handle edge case
//BUG: fix validation logic
Completely allowed in commits ✅
Shows in sidebar for organization 📋

🚀 Quick Start

Install the extension from VS Code Marketplace
Open any project - Todo Paranoid activates automatically
Look for the shield icon 🛡️ in your sidebar
Write a test comment: //PARANOID: testing this extension
Try to commit - it will be blocked! 🚫

📸 Screenshots

Todo Paranoid Panel The sidebar panel shows all your comments organized by type

Blocking comments are highlighted in red and prevent commits

⚙️ Configuration

Open VS Code Settings (Ctrl+,) and search for "Todo Paranoid":

🚫 Blocking Words (Prevent Commits)

{
  "todoParanoid.blockingWords": ["PARANOID", "NOCOMMIT", "URGENT", "CRITICAL"]
}

📝 Tracking Words (Organization Only)

{
  "todoParanoid.trackingWords": [
    "TODO",
    "FIXME",
    "BUG",
    "HACK",
    "NOTE",
    "REVIEW",
    "OPTIMIZE",
    "REFACTOR"
  ]
}

🔧 Other Settings

{
  "todoParanoid.enabled": true,
  "todoParanoid.blockGitOperations": true,
  "todoParanoid.showNotifications": true,
  "todoParanoid.fileExtensions": [
    ".js",
    ".ts",
    ".jsx",
    ".tsx",
    ".py",
    ".java",
    ".cpp",
    ".c",
    ".cs",
    ".php",
    ".rb",
    ".go"
  ]
}

🔐 Dual Protection System

Todo Paranoid uses two independent protection mechanisms for maximum security:

🛡️ Git API Integration (VS Code)

Intercepts commits directly within VS Code
Works automatically when extension is active
Can be toggled on/off instantly

🔒 Git Hook Protection (Terminal)

Creates physical git hooks in .git/hooks/pre-commit
Blocks commits even from external terminals
Persists even if extension is disabled

🎛️ Managing Protection

⚡ Quick Toggle (Git API Only)

Press Ctrl+Shift+P → Todo Paranoid: Toggle Todo Paranoid ON/OFF
Instantly enables/disables commit blocking within VS Code
Doesn't affect physical git hooks

🔧 Setup Git Hooks

Press Ctrl+Shift+P → Todo Paranoid: Setup Git Hook Protection
Creates physical git hook for terminal protection
Blocks commits from any git client

🧹 Complete Removal

Press Ctrl+Shift+P → Todo Paranoid: Remove ALL Protections (Git API + Hooks)
Removes both VS Code integration AND physical git hooks
Use this when switching between projects with different accounts

🔍 Diagnostic Tools

Press Ctrl+Shift+P → Todo Paranoid: Analyze Git Hooks
Shows detailed report of all git hooks in your repositories
Helps identify protection status

🗑️ IMPORTANT: Uninstalling Todo Paranoid

⚠️ CRITICAL NOTICE: Git hooks created by Todo Paranoid will persist after uninstalling the extension. This is intentional for security, but you need to clean them up manually.

🔴 BEFORE Uninstalling (Recommended Method)

Open Command Palette: Ctrl+Shift+P
Run cleanup command: Todo Paranoid: Remove ALL Protections (Git API + Hooks)
Confirm removal when prompted
Now you can safely uninstall the extension from Extensions panel

🟡 AFTER Uninstalling (If You Forgot to Clean Up)

If you already uninstalled and git commits are still being blocked:

Single Repository Cleanup:

# Check if the hook exists
ls -la .git/hooks/pre-commit

# Remove the Todo Paranoid hook
rm .git/hooks/pre-commit

# Verify it's gone
ls -la .git/hooks/pre-commit

Multiple Repositories Cleanup:

# Find and remove all Todo Paranoid hooks in current directory and subdirectories
find . -name ".git" -type d -exec sh -c 'if [ -f "$1/hooks/pre-commit" ]; then echo "Removing hook from: $1"; rm "$1/hooks/pre-commit"; fi' _ {} \;

Windows Users:

# PowerShell command to remove hooks
Get-ChildItem -Path . -Recurse -Directory -Name ".git" | ForEach-Object {
    $hookPath = Join-Path $_ "hooks\pre-commit"
    if (Test-Path $hookPath) {
        Write-Host "Removing hook from: $_"
        Remove-Item $hookPath
    }
}

🚨 Why Don't Hooks Auto-Remove?

Security Feature: Prevents accidental removal of commit protections
Team Safety: Ensures hooks persist even if someone accidentally disables the extension
Cross-Platform: Works independently of VS Code and the extension

✅ Verification After Cleanup

Test that hooks are completely removed:

# This should work without any blocking
echo "test" > test.txt
git add test.txt
git commit -m "test commit"
git reset --soft HEAD~1  # Undo the test commit
rm test.txt              # Clean up test file

🔒 How Protection Works

# ✅ This will work (saving and testing)
git add .

# ❌ This will be BLOCKED if you have blocking comments
git commit -m "my changes"

# Console output:
# 🚫 Todo Paranoid: Cannot commit! BLOCKING comments found:
# 📁 auth.js (Line 15): PARANOID
# 💡 Remove these comments before committing!

🏠 Is It Safe?

✅ Completely local - only affects YOUR machine
✅ Not shared - doesn't modify the shared repository
✅ Optional - team members can choose to use it or not
✅ Removable - can be disabled anytime with "Remove ALL Protections"

🎮 Commands Reference

Open Command Palette (Ctrl+Shift+P) and use these commands:

Command	Description
`Todo Paranoid: Scan Workspace for Comments`	Manually refresh the comments panel
`Todo Paranoid: Toggle Todo Paranoid ON/OFF`	Enable/disable Git API integration
`Todo Paranoid: Setup Git Hook Protection`	Install Git pre-commit hook for terminal protection
`Todo Paranoid: Remove ALL Protections (Git API + Hooks)`	Complete removal - disables everything

🚨 Multi-Account Git Workflow

Working with different Git accounts? Todo Paranoid's dual protection can interfere when switching between projects. Here's the workflow:

🔄 When Switching Projects/Accounts:

Before switching accounts:

Ctrl+Shift+P → "Todo Paranoid: Remove ALL Protections"

Switch to new account/project

If you want protection in new project:

Ctrl+Shift+P → "Todo Paranoid: Setup Git Hook Protection"

🧹 Emergency Cleanup (if commits are blocked unexpectedly):

# Remove git hooks manually
rm .git/hooks/pre-commit

# Or clean all repositories at once
find . -name ".git" -type d -exec rm -f {}/hooks/pre-commit \;

🤝 Perfect for Teams

👥 Team Lead

// Add to .vscode/settings.json (shared)
{
  "todoParanoid.blockingWords": ["PARANOID", "NOCOMMIT", "DELETEME"],
  "todoParanoid.trackingWords": ["TODO", "FIXME", "BUG", "REVIEW"]
}

Each team member can:

✅ See the same comment categories (from shared settings)
✅ Choose their own protection level (personal preference)
✅ Customize additional words (personal productivity)

📊 Use Cases

🧪 Testing & Development

function authenticate(user) {
  // PARANOID: using fake data for testing
  return { token: 'fake_token_123' };

  // TODO: implement real authentication
  // return realAuth(user);
}

✅ Can save and test this code
❌ Cannot commit the "PARANOID" line
✅ Can commit with the "TODO" line

🔒 Security & Secrets

def connect_database():
    # NOCOMMIT: remove hardcoded password
    password = "admin123"

    # TODO: get password from environment
    # password = os.getenv('DB_PASSWORD')

    return connect(password)

🚀 Production Deployments

const API_URL =
  process.env.NODE_ENV === 'production'
    ? 'https://api.myapp.com'
    : 'http://localhost:3000'; // PARANOID: should be production URL

// FIXME: add error handling for API calls

🎨 Visual Indicators

Type	Highlight	Sidebar Icon	Action
🚫 Blocking	Red border	● Red circle	Blocks commits
📝 Tracking	Yellow border	○ Orange circle	Allows commits

⚡ Performance

🚀 Fast scanning - Only scans when files change
💾 Low memory - Minimal resource usage
⚙️ Smart updates - Auto-refreshes when you save files
🎯 Targeted - Only scans relevant file extensions

🔧 Troubleshooting

Panel Not Showing Comments?

Check if your file extension is supported (see settings)
Press Ctrl+Shift+P → Todo Paranoid: Scan Workspace for Comments
Verify todoParanoid.enabled is true in settings

🔴 Git Hook Still Blocking After Extension Removal?

This is the most common issue! Git hooks are physical files that persist even after uninstalling the extension.

⚡ Quick Fix:

rm .git/hooks/pre-commit

🧹 Complete Fix (Multiple Repositories):

# Find and remove all Todo Paranoid hooks
find . -name ".git" -type d -exec rm -f {}/hooks/pre-commit \;

🔍 Check What's Blocking You:

# View the hook content to confirm it's from Todo Paranoid
cat .git/hooks/pre-commit

# Look for this line at the top:
# "# Todo Paranoid pre-commit hook"

Comments Not Highlighted?

Make sure you're using the correct comment format: // or #
Check todoParanoid.showNotifications is enabled
Try switching to a different file and back

Extension Seems Disabled But Still Blocking?

This means git hooks are still active. Solution:

Check if hooks exist: ls -la .git/hooks/pre-commit
Remove them: rm .git/hooks/pre-commit
Or use the extension's cleanup command (if still installed):
```
Ctrl+Shift+P → "Todo Paranoid: Remove ALL Protections"
```

📝 Changelog

Changelog

[0.0.20] - 2025-06-02

🚀 Performance Improvements

Asynchronous file scanning: Complete rewrite of scanning engine to use async operations, eliminating UI freezing
Smart caching system: Files are cached based on modification time, avoiding unnecessary re-scans
Batch processing: Large file sets are processed in batches to maintain UI responsiveness
Progress indicators: Added progress bars for long-running scan operations

🛡️ Enhanced Folder Exclusion

Comprehensive exclusion list: Now excludes common build/cache folders by default:
- node_modules, .next, dist, build, out, target
- vendor, .vscode, coverage, .nyc_output, __pycache__
- .cache, tmp, temp
Pattern-based exclusion: Uses VS Code's efficient findFiles API with glob patterns
Configurable exclusions: Users can customize excluded folders via settings

⚙️ New Configuration Options

todoParanoid.maxFiles: Set maximum number of files to scan (default: 5000)
todoParanoid.excludeFolders: Customize which folders to exclude from scanning
Improved file extension handling: More efficient filtering of file types

🔧 Technical Improvements

Debounced file watchers: Prevents excessive refreshes when multiple files change
Better error handling: More robust error reporting and recovery
Memory optimization: Reduced memory usage for large codebases
Cleaner cache management: Automatic cleanup of stale cache entries

🐛 Bug Fixes

Fixed issue where node_modules subdirectories were still being scanned
Resolved UI blocking issues in large projects (1000+ files)
Improved regex matching for comment detection
Fixed decoration cleanup when switching between files

📊 Performance Metrics

Before: ~10-15 seconds for 1000 files (with UI freeze)
After: ~2-3 seconds for 1000 files (with progress indicator, no freeze)
Memory usage: Reduced by ~40% in large projects
CPU usage: Significantly lower during background scanning

💡 For Large Projects

This release specifically addresses performance issues reported in large Next.js projects and similar codebases with thousands of files. The extension now scales efficiently and won't impact your development workflow.

[0.0.18] - 2025-05-31

🔧 Fixed

Git Hook Consistency: Fixed inconsistent regex patterns between VS Code detection and Git pre-commit hooks
- Git hooks now properly block comments with spaces like // PARANOID and //PARANOID consistently
- Unified regex pattern across all blocking mechanisms (Git API, Git hooks, and visual highlighting)
- Resolved issue where comments were visually highlighted but not blocked during commit operations

🎨 Improved

Enhanced Visual Highlighting: Updated comment highlighting with improved colors and styling
- Blocking comments now use red theme (#f85149) with subtle background and border
- Tracking comments use amber theme (#fbbc04/#bf8700) for better visual distinction
- Added bold font weight for blocking comments and medium weight for tracking comments
- Improved border radius and opacity for better readability

🚀 Enhanced

Stricter Pattern Matching: All blocking mechanisms now use consistent strict regex patterns
- Comments must start with // or # followed by optional whitespace, then the blocking word
- Prevents false positives like // This code is PARANOID from being blocked
- Maintains protection for legitimate blocking comments like // PARANOID: test data

[0.0.15] - 2025-05-29

✨ Initial release
🛡️ Blocking and tracking comment detection
🎨 Visual highlighting in editor
📋 Sidebar panel with organized view
🔐 Optional Git hook protection
⚙️ Fully configurable word lists

❤️ Support Todo Paranoid

If Todo Paranoid has saved you from embarrassing commits, consider supporting its development:

Your support helps keep this project alive and improving! 🚀

🐛 Issues & Feature Requests

Found a bug or have a feature request?

📄 License

Made with ❤️ for developers who care about clean commits

Todo Paranoid - Block Forbidden Comments

mobius1983