name: File Validation description: Strict detection and removal of unrelated files before PR creation

File Validation Skill

Be strict, not permissive. Unrelated files MUST be removed, not suggested.

Core Principle: STRICT MODE - Unrelated files are removed immediately, not flagged for later cleanup.

Overview

File validation ensures PRs contain only relevant changes. This prevents:

• Local dev artifacts (redis-cluster, .env.local, tmp/)
• Debug files (console.log, dump.rdb)
• OS/IDE artifacts (.DS_Store, .vscode/)
• Unintentional changes from other work

Policy: When unrelated files are detected, remove them. Don't suggest cleanup - do it.

When to Use

Trigger automatically during:

• /commit-commands:commit-push-pr
• /commit-commands:commit
• Any PR creation workflow

Trigger manually with:

• /v-file-validation:check

Commands

Detection Patterns

By File Path

Flag files containing these path segments:

By File Extension

Flag files with these extensions:

By File Name

Flag files matching these names:

Common Categories

Detection Logic

def is_unrelated(file_path, pr_scope):
    # 1. Path-based detection
    unrelated_patterns = [
        'local', 'test-data', 'tmp', 'debug', 'dump',
        'cache', '.DS_Store', '*.log', '*.pid',
        'redis-cluster', 'docker-compose.override'
    ]

    if any(pattern in file_path for pattern in unrelated_patterns):
        return True

    # 2. Extension-based detection
    unrelated_extensions = ['.log', '.pid', '.rdb', '.dump', '.swp', '.pyc']
    if any(file_path.endswith(ext) for ext in unrelated_extensions):
        return True

    # 3. Scope-based detection
    # Read PR description + Linear issue
    # Check if file is mentioned or relates to scope
    if not file_mentioned_in_scope(file_path, pr_scope):
        return True

    return False

Strict Mode Policy

Wrong Approach (Too Permissive)

❌ "These files shouldn't affect the PR, but you may want to clean them up later"

Right Approach (Strict)

✅ "These files are unrelated to this PR and must be removed:
- redis-cluster/dump.rdb (local dev artifact)
- .env.local (local config)
- tmp/debug.log (debug file)

Removing them now."

Then execute the removal.

Handling User Override

Rare case: User insists files ARE related.

Response:

Okay, keeping the files. Please add justification to PR description:

## Unusual Files Included

This PR includes files that may appear unrelated:
- redis-cluster/: [Explain why needed]
- .env.local: [Explain why needed]

Justification: [User's explanation]

This documents the decision for reviewers.

Integration Points

With commit-commands Plugin

When /commit-commands:commit-push-pr runs:

1. List all changed files
2. Invoke /v-file-validation:check
3. If unrelated files found → Prompt for removal
4. After cleanup → Continue with commit

With Tech Lead

Before tech lead approval:

1. Run file validation
2. If unrelated files found → Block until cleaned

Reference Files

Skill Version: 1.0.0