Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
aeondave/test-driven-developmentIngeniería inversa y fuzzing

test-driven-development

⁨Develop behavior through a failing test or reproducer, implementation, and refactoring. Use when test-first development is requested or a new behavior or bug fix benefits from an executable regression before implementation.⁩

v2026.11.13-21cd5683 instalaciones+3 en 7 días39 EstrellasMITsincronizado hace 11 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/test-driven-development

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
k5ylkBnFdI…O5nBb3Aw==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete976c39a7…2c3dd80f
976c39a7f848…0dc42c3dd80f1 archivo · ⁦1.8 KB⁩
EscaneoBajosin hallazgos
El escaneo no encontró nada que señalar en esta versión.Ver el escaneo completo
Fuentegithub.com/AeonDave/malskill/tree/main/coding-behaviours/test-driven-development@21cd568

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

Make the intended behavior observable before implementing it, then use the check to guide a small complete change. A passing test supports the behavior it covers; it is not a proof of correctness.

Choose the appropriate entry point

  • For a new behavior or reproducible bug, use the failing-check loop below when practical. Follow explicit user and repository testing requirements.
  • For a behavior-preserving refactor, establish a passing baseline and add characterization only for relevant uncovered behavior. Keep those checks green; do not manufacture a failure for behavior that should stay unchanged.
  • For code already written, preserve it and assess the missing verification. Add meaningful checks; use an isolated pre-change baseline or controlled fault to test their sensitivity when useful. Do not discard work or restart implementation merely to recreate test-first history.
  • For exploration, configuration, generated artifacts, or changes that do not benefit from a new automated test, choose the appropriate existing check, generator test, static validation, or reproducible manual procedure. State what remains unverified; do not describe tests written afterward as a test-first sequence.

For an urgent incident, use systematic-debugging to prioritize authorized mitigation and preserve evidence. Missing deterministic reproduction does not forbid investigation or recovery.

RED-GREEN-REFACTOR

  1. Specify one behavior and its observable outcome. Reuse a relevant existing check or failing artifact rather than creating a duplicate.
  2. RED: write the smallest useful test/reproducer and run it. Confirm that failure represents the missing behavior or defect; distinguish an intentionally absent API from an unrelated import, fixture, or environment error.
  3. GREEN: implement the smallest complete change that satisfies the behavior. Run the focused check and relevant neighboring cases; do not weaken assertions to make it pass.
  4. REFACTOR: improve the affected structure while preserving the contract and keeping checks green. Use software-architecture for consequential design or simplification decisions.
  5. Continue and verify: take the next behavior when needed and run applicable broader checks. Use verification-before-completion for required gates, evidence freshness, and completion claims.

Diagnose an unexpected test result

  • If a proposed regression already passes, check whether the behavior exists, the intended path ran, and the chosen input/assertion can detect the defect. A passing characterization test is expected.
  • If setup fails, repair the relevant fixture or environment before treating the result as evidence about the behavior.
  • If setup is excessive, inspect the test scope and existing seams before changing production APIs. Use testing-reliability for weak assertions, misleading doubles, fixture coupling, or flakes.

Apply to security tooling

For parsers, exploit harnesses, or payload tooling, preserve the relevant input, seed, transcript, or artifact before changing code and turn it into a bounded local regression where practical. Use testing-reliability for what the assertion must establish and the language/domain testing skill for harness mechanics.

Use software-guidelines for patch scope and affected consumers. Language-specific testing skills own framework syntax and execution commands.

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellNoNo
Usa la redNoNo
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

El escaneo no encontró nada que señalar en esta versión.

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.11.13-21cd56813 nov 202621cd568976c39a7Firmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login