File Validation for Clean PRs FAQs

Question 1

Can I prevent a specific file from being removed if it's actually needed?

Accepted Answer

Yes. If a user insists a file is related, the skill allows an override but requires the user to add a justification to the PR description for reviewers to see.

Question 2

Why is 'Strict Mode' used instead of just suggesting changes?

Accepted Answer

Strict Mode ensures that unrelated files are removed immediately to prevent accidental commits, reducing the cognitive load on reviewers and maintaining a clean git history.

Question 3

How does it handle different operating systems and IDEs?

Accepted Answer

The skill includes broad patterns for common OS artifacts (macOS, Windows) and IDE files (VS Code, IntelliJ, Vim) to ensure a clean repository regardless of the developer's environment.

Question 4

What files does the File Validation skill remove?

Accepted Answer

It targets local development artifacts like .env.local, debug logs, database dumps, OS metadata (.DS_Store), IDE settings, and temporary build artifacts.

Question 5

Does this skill run automatically?

Accepted Answer

Yes, it is designed to trigger automatically during commit-push and PR creation workflows, but it can also be manually invoked using the /v-file-validation:check command.

File Validation for Clean PRs

主要功能

使用场景

File Validation for Clean PRs

主要功能

使用场景