File Validation
Strict detection and removal of unrelated files before PR creation
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill File Validationgit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/file-validation ~/.claude/skills/File-ValidationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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 | Command | Purpose | |---------|---------| | `/v-file-validation:check` | Run detection and prompt for removal | --- ## Detection Patterns ### By File Path Flag files containing these path segments: | Pattern | Category | Example | |---------|----------|---------| | `local` | Local config | `config/local.json` | | `test-data` | Test fixtures | `test-data/users.json` | | `tmp` | Temporary | `tmp/debug.log` | | `debug` | Debug files | `debug/output.txt` | | `dump` | Data dumps | `dump/database.sql` | | `cache` | Cache files | `.cache/` | | `redis-cluster` | Local Redis | `redis-cluster/dump.rdb` | | `docker-compose.override` | Local Docker | `docker-compose.override.yml` |
Details
- Skill name
File Validation- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/file-validation/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the File Validation skill do?
Strict detection and removal of unrelated files before PR creation
How do I install the File Validation skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is File Validation popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
Finishing a Development Branch
8Freddy-CHEN-ux/00_claude_skills
Use when ready to merge feature branch. Complete checklist before creating PR/MR. Ensures professional quality and prevents embarrassing mistakes.
Continuous Delivery
5vnovakovits/claude-skills
Apply Jez Humble and David Farley's Continuous Delivery — the discipline of making software always release-ready through deployment pipelines, trunk-based development, automated everything, feature flags, branch-by-abstraction, and the four DORA metrics (deployment frequency, lead time, change failure rate, mean time to restore). Use when designing a deployment pipeline, choosing a branching strategy, debating long-lived feature branches vs. trunk-based, deciding how to deploy in-flight changes safely, or evaluating delivery health.
Git Commit Message
8Freddy-CHEN-ux/00_claude_skills
Auto-generates conventional commit messages from git diffs with tiered format enforcement. Analyzes staged changes to produce meaningful commit messages following Conventional Commits specification.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.