agentsclimarketplace
Sign in

Final delivery validation

Skill nathaliafab/proftest2/.github/skills/final-delivery-validation

Validate final software delivery with Docker-only build and tests, plus risk and documentation checklists. Use when finishing a task, before merge, before PR review, or release readiness checks.From its SKILL.md

Install
npx -y skills add nathaliafab/proftest2 --skill final-delivery-validation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, 610 tokens by cl100k_base, as published. Nobody here has run it

Final Delivery Validation

Valida a entrega final de uma tarefa com foco em confiabilidade, regressao e completude de documentacao.

Quando usar

  • No fim de qualquer implementacao com alteracao de codigo.

Politica obrigatoria

  • Use apenas comandos via Docker Compose.
  • Nao executar npm, node ou npx diretamente no host.
  • Comandos devem usar caminho explicito: sistema/docker-compose.yml.

Entradas esperadas

  • Escopo alterado (arquivos, modulos ou funcionalidades).
  • Criticos de negocio afetados.
  • Definicao de pronto.

Procedimento

  1. Mapear escopo de mudanca e riscos principais
  • Liste funcionalidades afetadas.
  • Identifique pontos de regressao provavel.
  1. Validar build e tipagem via Docker
  • Servidor: docker compose -f sistema/docker-compose.yml run --rm server npm run build
  • Cliente: docker compose -f sistema/docker-compose.yml run --rm client npm run build
  1. Executar testes via Docker
  • Suite de testes: docker compose -f sistema/docker-compose.yml run --rm tests npm test
  • Se houver teste direcionado no projeto, execute tambem o subconjunto relevante.
  1. Checklist de risco
  • Nao houve quebra de API/contrato sem alinhamento explicito.
  • Entradas invalidas sao tratadas com erro controlado.
  • Fluxos criticos possuem cobertura de teste suficiente.
  • Nao foram introduzidas dependencias inseguras ou sem necessidade.
  • Nao existem segredos hardcoded.
  • Erros sao tratados sem vazar detalhes sensiveis.
  1. Checklist de documentacao
  • README/guia operacional atualizado quando houve mudanca de uso ou setup.
  • Mudancas de comportamento foram documentadas.
  • Novas variaveis de ambiente foram documentadas.
  • Limitacoes conhecidas e pendencias foram registradas.
  • Instrucoes de execucao continuam Docker-only.
  1. Relatorio final de validacao
  • Informe status de cada etapa (build, testes, risco, documentacao).
  • Liste falhas encontradas com impacto, severidade e recomendacao.
  • Se tudo estiver ok, declarar entrega apta para review/merge.

Formato de saida

Retorne sempre:

  1. Escopo validado
  2. Resultado de build
  3. Resultado de testes
  4. Riscos identificados e severidade
  5. Estado da documentacao
  6. Veredito final (Aprovado, Aprovado com ressalvas, Reprovado)

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most quality gates skills give in 610 tokens

Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-07

  • Read the output and check the exit codein 54 of 1195, across 14 files
  • Verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
  • Identify the verification command proving the claimin 51 of 1195, across 12 files
  • Run the full verification commandin 50 of 1195, across 11 files
  • Verify output confirms the claimin 49 of 1195, across 12 files
  • Check version control diff after agent delegationin 46 of 1195, across 6 files
  • State claim with evidencein 44 of 1195, across 4 files
  • Run the test suitein 33 of 1195, across 26 files
  • Keep state in memory by defaultin 27 of 1195, across 6 files
  • Make prototype runnable with one commandin 26 of 1195, across 5 files
  • Produce a verification reportin 25 of 1195, across 14 files
  • Detect the package manager from lockfilesin 24 of 1195, across 5 files

Said here and by no other author read

  • map change scope and main risks
  • list affected functionalities
  • identify likely regression points
  • validate build and typing via docker
  • execute test suite via docker
  • run relevant targeted tests

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,401. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.