quality-assurance
Maintains code quality by mandating tests before and after implementation.
Install
mkdir -p .claude/skills/quality-assurance-joleques && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13357" && unzip -o skill.zip -d .claude/skills/quality-assurance-joleques && rm skill.zipInstalls to .claude/skills/quality-assurance-joleques
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Regras para TDD, gate de testes antes e depois da implementacao, avaliacao de qualidade dos testes e proibicao de remover testes apenas para fazer a suite passar.Key capabilities
- →Ensure every new artifact requires a corresponding test.
- →Require unit tests for bugs and implementations.
- →Reproduce bugs with tests to prevent recurrence.
- →Execute the relevant test suite before implementation.
- →Report PASS or FAIL after implementation.
- →Evaluate the quality of created or altered tests.
How it works
This skill enforces a Test-Driven Development (TDD) workflow by requiring test execution before and after implementation, evaluating test quality, and prohibiting practices that compromise test integrity.
Inputs & outputs
When to use quality-assurance
- →Enforcing TDD workflows
- →Preventing regressions
- →Reviewing test coverage quality
About this skill
🧪 Regras de Testes e Qualidade
🎯 Cobertura Minima
- Todo novo artefato exige teste correspondente.
bugeimplementacaoexigem testes unitarios.- Em
bug, o teste deve reproduzir o problema e impedir recorrencia. - Foco principal: testes unitarios. Integracao entra em pontos criticos quando necessario.
- Testes de API: usar mocks para HTTP/DB quando o contexto pedir isolamento.
🚀 Fluxo Obrigatorio
Estas regras se aplicam quando a demanda envolve implementacao: bug ou implementacao.
Para analise, nao ha obrigacao de rodar testes antes ou depois, porque nao ha mudanca de implementacao.
Antes de implementar
- Execute a suite de testes relevante.
- Defina e reporte o escopo minimo da baseline (modulo afetado + regressao relacionada).
- Se a suite falhar antes da mudanca, interrompa o trabalho.
- Analise a falha e discuta com o usuario antes de seguir.
Durante a implementacao
- Nao trate teste como acessorio decorativo.
- Nao remova teste so para fazer a suite passar.
- Se um teste precisar ser removido por mudanca real de comportamento, registre a justificativa explicitamente.
Ao final da implementacao
- Execute os testes relevantes e reporte
PASSouFAIL. - Avalie a qualidade dos testes criados ou alterados.
- Verifique se os testes cobrem o comportamento pedido, nao apenas a linha feliz cosmetica.
🔍 Criterios de qualidade dos testes
- O teste falha sem a implementacao correta.
- O teste protege regra de negocio ou comportamento observavel.
- O teste tem nome claro e intencao legivel.
- O teste nao depende de excesso de mocks sem necessidade.
- O teste nao foi afrouxado artificialmente para aceitar comportamento incorreto.
🚫 Antipadroes proibidos
- Remover teste para maquiar suite verde.
- Alterar assercoes para algo vago so porque a implementacao nao sustentou o contrato.
- Declarar "nao aplicavel" para testes. Nesta base, teste sempre e aplicavel.
✅ Definition of Done (Geral)
- Código limpo e testado.
- Sem nomes genéricos.
- Logs estruturados em inglês via
logAdapter. - Testes executados antes e depois da implementacao.
- Qualidade dos testes analisada e reportada.
- Documentação sugerida/atualizada.
Saida estruturada obrigatoria
Ao concluir a revisao, responda com:
status:PASSouFAILbaseline_pre: comando(s) e resultado antes da implementacaovalidacao_pos: comando(s) e resultado apos a implementacaoachados: riscos de teste e coberturaacoes: correcoes obrigatorias antes de concluir
When not to use it
- →When the task is analysis and does not involve implementation changes.
- →When the task requires removing tests just to make the suite pass.
- →When the task involves altering assertions to be vague.
Limitations
- →It prohibits removing tests solely to make the suite pass.
- →It prohibits declaring 'not applicable' for tests, as tests are always applicable in this context.
How it compares
This skill establishes strict rules for test coverage and quality, ensuring that tests are integral to the development process and not merely an accessory, unlike development without enforced TDD principles.
Compared to similar skills
quality-assurance side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| quality-assurance (this skill) | 0 | 3mo | No flags | Intermediate |
| python-testing-patterns | 77 | 2mo | Review | Intermediate |
| fix-bug | 11 | 7mo | Review | Intermediate |
| test-fixing | 1 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
fix-bug
tddworks
Guide for fixing bugs in ClaudeBar following Chicago School TDD and rich domain design. Use this skill when: (1) User reports a bug or unexpected behavior (2) Fixing a defect in existing functionality (3) User asks "fix this bug" or "this doesn't work correctly" (4) Correcting behavior that violates the user's mental model
test-fixing
mhattingpete
Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.
fixing-bugs-systematically
CaptainCrouton89
Diagnose and fix bugs through systematic investigation, root cause analysis, and targeted validation. Use when something is broken, errors occur, performance degrades, or unexpected behavior manifests.
moai-workflow-testing
modu-ai
Comprehensive development workflow specialist combining DDD testing, debugging, performance optimization, code review, PR review, and quality assurance into unified development workflows
investigate
MadAppGang
Unified entry point for code investigation. Auto-routes to specialized detective based on query keywords. Use when investigation type is unclear or for general exploration.