file-name-wizard
Audit filename conventions across your codebase
Inconsistent naming conventions create confusion and technical debt. This skill systematically audits all filenames against your CLAUDE.md standards and identifies violations.
Baixar o ZIP da skill
Upload no Claude
Vá em Configurações → Capacidades → Skills → Upload skill
Ative e comece a usar
Testar
A utilizar "file-name-wizard". Audit naming conventions in my codebase
Resultado esperado:
- Found 47 naming issues across 312 files
- Critical: 3 files with version suffixes (-v2, -new)
- High: 12 files missing .service.ts suffix
- Medium: 18 files with wrong case convention
- Low: 14 files with redundant component suffix
- Most issues in src/services/ (15 files)
- Full report saved to .audits/naming-audit-2024-01-10.md
A utilizar "file-name-wizard". Check component naming
Resultado esperado:
- Audited 24 component files
- Found 5 issues with component naming
- 2 files using PascalCase instead of kebab-case
- 3 files with redundant 'component' suffix
- All issues documented in components-audit.md
A utilizar "file-name-wizard". Find temporary files
Resultado esperado:
- Found 8 files with temporary naming patterns
- 3 files with -v2 suffix
- 2 files with -new prefix
- 2 files named test.ts or temp.ts
- 1 file with -old suffix
- See full list with suggested renames in temp-files-report.md
Auditoria de Segurança
SeguroThis is a read-only audit tool with no security risks. The static analyzer flagged 89 potential issues, but ALL are false positives. The 'weak cryptographic algorithm' alerts trigger on documentation examples of file names like 'md5-hash.ts' and 'sha-utils.ts' - not actual crypto usage. The 'Ruby/shell backtick' alerts trigger on markdown code formatting backticks, not execution. The 'hardcoded URL' is legitimate source metadata. This tool only reads filenames and generates reports without modifying any files or accessing sensitive data.
Fatores de risco
🌐 Acesso à rede (1)
⚙️ Comandos externos (79)
Pontuação de qualidade
O Que Você Pode Construir
Establish coding standards
Audit existing codebase to identify inconsistent naming patterns before creating team-wide standards
Pre-merge quality checks
Run naming audits before code reviews to catch naming convention violations early
Legacy codebase cleanup
Identify systematic naming issues across large codebases to plan refactoring efforts
Tente Estes Prompts
Please audit all filenames in this codebase for naming convention violations and inconsistencies
Audit the components directory for proper React component naming conventions and identify any violations
Analyze all service files to ensure they follow the *.service.ts naming pattern and identify outliers
Find all files with temporary naming patterns like -v2, -new, -old and suggest proper names
Melhores Práticas
- Run audits before establishing new naming standards
- Address critical issues (temporary files) immediately
- Use audit reports to create CLAUDE.md documentation
Evitar
- Ignoring audit results without addressing issues
- Using audit to shame developers rather than improve
- Running audits too frequently without action
Perguntas Frequentes
Does this tool rename files automatically?
What file types does it check?
How does it know the naming standards?
Where are audit reports saved?
Can it fix the issues it finds?
Is it safe to run on production code?
Detalhes do Desenvolvedor
Estrutura de arquivos
📄 SKILL.md