pre-flight-check
Skill0 starsChanged 3 months agoMITView on GitHub
Validação local obrigatória antes de qualquer modificação estrutural, refatoração ou deploy. Roda type-check, testes e build. Bloqueia se qualquer etapa falhar. Triggers: "pre-flight-check", "pre flight", "validar antes de deploy", "checar build", "rodar testes", "verificar antes de commit"
3 other projects use a version of this.
Adopted by
Most recently taken up by
- mirekondro/The-Pre-Flight-Checktheir own version, first seen Oct 13, 2026
- MyAiFreedomSystems/pre-flight-checktheir own version, first seen Aug 14, 2026
- pskoett/pskoett-ai-skillstheir own version, first seen Apr 13, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- pskoett/pskoett-ai-skills★ 327same name
- mirekondro/The-Pre-Flight-Check★ 2same name
- MyAiFreedomSystems/pre-flight-check★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- blueprint-verticalSkill
- cavemanSkill
- fabrica-listasSkill
- headroomSkill
- lean-ctxSkill
- rtk-memorySkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Commit de mudanças estruturais
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pre-flight Check
Protocolo obrigatório de validação local. DEVE ser executado ANTES de:
- Qualquer deploy
- Commit de mudanças estruturais
- Refatoração de service layer
- Alterações em types.ts ou module.ts
Passo a passo
- Type check:
npm run check:types(ounpx tsc --noEmit). - Testes:
npm run test:safe(ounpx vitest run). - Build:
npm run build. - Análise: se qualquer etapa falhar → PARAR, corrigir, repetir do passo 1.
- Reportar: listar resultados de cada etapa.
Ordem rigorosa (NUNCA alterar)
1. Type Check → 2. Testes → 3. Build → 4. DeployNUNCA pular etapas. NUNCA rodar build antes de testes. NUNCA deploy antes de build.
Regras
Se type check falhar
- Ler erro via headroom (compactar output).
- Diagnosticar via lean-ctx (ler apenas assinaturas afetadas).
- Corrigir o tipo.
- REINICIAR do passo 1 (type check novamente).
Se testes falharem
- Aplicar headroom no output do vitest.
- Identificar teste que falhou (arquivo + linha).
- Ler teste + código testado via lean-ctx.
- Corrigir código OU teste (conforme a intenção).
- REINICIAR do passo 1.
Se build falhar
- Aplicar headroom no output do build.
- Geralmente é erro de tipo não detectado no passo 1 (dependências circulares, etc.).
- Corrigir e REINICIAR do passo 1.
Se tudo passar
- Reportar:
✓ types | ✓ testes | ✓ build — pronto para deploy - Prosseguir com ação solicitada.
NUNCA fazer
- NUNCA declarar tarefa como concluída sem rodar pre-flight-check.
- NUNCA fazer deploy com testes falhando.
- NUNCA pular type check "porque é mudança pequena".
- NUNCA usar
--no-verifypara pular hooks de validação. - NUNCA ignorar warnings de deprecated sem avaliar impacto.
- NUNCA rodar pre-flight-check em background — é bloqueante.
- NUNCA alterar a ordem dos passos.
Interação com outras skills
- headroom: OBRIGATÓRIO antes de reportar falhas (compactar output de erro).
- lean-ctx: usado para diagnosticar erros identificados no pre-flight.
- caveman: resultado do pre-flight pode ser reportado em modo caveman.
- rtk-memory: erros novos descobertos devem ser registrados.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

