Skill post-patch-validation
✓ OficialscriptsValida parches de seguridad comparando el código base y el parcheado mediante exploits reproducibles, variantes de la causa raíz y comprobaciones de regresión.
- Estrellas en GitHub
- 8136
- Archivos
- 5
- Último commit
- 11 nov 2026
- Licencia
- CC-BY-SA-4.0
- Herramientas permitidas
- 7
¿Qué hace la skill post-patch-validation?
Valida parches de seguridad comparando el código base y el parcheado mediante exploits reproducibles, variantes de la causa raíz y comprobaciones de regresión.
Resumen generado a partir del SKILL.md de la skill.
Sobre la skill post-patch-validation
Los ingenieros de seguridad y desarrolladores utilizan esta skill para verificar que un parche de seguridad realmente soluciona una vulnerabilidad sin introducir nuevos errores ni romper la funcionalidad existente. Funciona comparando una base vulnerable contra una versión parcheada del código mediante un plan de validación estructurado. El proceso consiste en ejecutar los exploits originales, probar variantes de la causa raíz, buscar regresiones y asegurar que el comportamiento legítimo de la aplicación permanezca sin cambios.
Un agente debe cargar esta skill después de que exista un parche o un commit de remediación, pero antes de que se fusione o se reporte como solucionado. Se apoya en un script de orquestación basado en Python para estructurar, validar y ejecutar los planes de evidencia. La herramienta genera resultados detallados que incluyen un resumen en JSON, un informe en markdown y directorios temporales archivados para cada comprobación. Está diseñada para la ejecución local en repositorios y requiere autorización explícita para ejecutar código o suites de pruebas. A diferencia de las revisiones simples de diff, esta skill proporciona evidencia concreta mediante aserciones en tiempo de ejecución y ejecución ciega para evitar falsos positivos.
Lo que un agente puede hacer con ella
- 1Validar parches de seguridad generados por IAVerifica que un parche producido por un agente de IA remedie correctamente una vulnerabilidad antes de que un humano revise el código.
- 2Detectar variantes de la causa raízAsegura que una solución cubra todas las formas posibles en que se puede activar una vulnerabilidad específica, en lugar de limitarse a una sola ruta de exploit.
- 3Prevenir regresiones de seguridadComprueba si una corrección de seguridad introduce inadvertidamente una nueva vulnerabilidad en rutas de código adyacentes.
- 4Confirmar la preservación del comportamientoVerifica que la remediación de seguridad no cambie el resultado esperado de las funciones de la aplicación que no se ven afectadas.
Escrito a partir del SKILL.md de la skill. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar la skill post-patch-validation
Cada comando copia la carpeta de la skill al directorio de skills del cliente. Reinicia el cliente o inicia una nueva sesión para cargarla.Instalar la skill post-patch-validation en Plugin
/plugin marketplace add trailofbits/skills /plugin install post-patch-validation@trailofbits
Instalar la skill post-patch-validation en Claude Code
~/.claude/skills/post-patch-validation/SKILL.md
$ npx degit trailofbits/skills/plugins/post-patch-validation/skills/post-patch-validation ~/.claude/skills/post-patch-validationInstalar la skill post-patch-validation en Claude Code (project)
.claude/skills/post-patch-validation/SKILL.md
$ npx degit trailofbits/skills/plugins/post-patch-validation/skills/post-patch-validation .claude/skills/post-patch-validationInstalar la skill post-patch-validation en Codex
~/.agents/skills/post-patch-validation/SKILL.md
$ npx degit trailofbits/skills/plugins/post-patch-validation/skills/post-patch-validation ~/.agents/skills/post-patch-validationInstalar la skill post-patch-validation en Gemini CLI
~/.gemini/skills/post-patch-validation/SKILL.md
$ npx degit trailofbits/skills/plugins/post-patch-validation/skills/post-patch-validation ~/.gemini/skills/post-patch-validationInstalar la skill post-patch-validation en Claude.ai
npx degit trailofbits/skills/plugins/post-patch-validation/skills/post-patch-validation post-patch-validation && zip -r post-patch-validation.zip post-patch-validation # claude.ai → Customize → Skills → + → Create skill → Upload a skill → post-patch-validation.zip
Verificaciones automáticas
Ejecutado 15 nov 2026Informe completo →Aún sin verificar. Una skill necesita 80 puntos, ningún hallazgo grave y datos suficientes para comprobarla. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesibletrailofbits/skills/plugins/post-patch-validation/skills/post-patch-validation is public and reachablegithub.com/trailofbits/skills/tree/HEAD/plugins/post-patch-v ↗Aprobado
- Licencia de código abierto (OSI)CC-BY-SA-4.0 is not OSI-approvedspdx.org/licenses/CC-BY-SA-4.0.html ↗Hallazgo
- Commit o lanzamiento en el último añoLast commit 2026-11-11github.com/trailofbits/skills/commits ↗Aprobado
- Sin descargar y ejecutar ni robo de credenciales en los scripts1 script read; no download-and-run, remote eval, base64 execution or credential uploadAprobado
- Sin instrucciones ocultas en SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/trailofbits/skills/blob/HEAD/plugins/post-patch-v ↗Aprobado
- Las herramientas preaprobadas están acotadasBash lets the agent run any shell command without askinggithub.com/trailofbits/skills/blob/HEAD/plugins/post-patch-v ↗Hallazgo
- SKILL.md sigue el formato de Agent SkillsValid name and description; says when to use it; 262 linesgithub.com/trailofbits/skills/blob/HEAD/plugins/post-patch-v ↗Aprobado
SKILL.md
Ver en GitHubPost-Patch Validation
Validate a security patch against the reported bug and the surrounding code it affects. Give the patch author reproducible failures to fix and identify what still needs testing. Apply the same checks to human and agent patches. The diff, author, upstream implementation, and original proof of concept alone cannot establish correctness.
When to Use
- A security fix, remediation commit, patch file, or pull request already exists.
- An AI-generated patch needs validation before human review or merge.
- A fix may cover one exploit path while missing variants of the same root cause.
- A security fix may alter legitimate behavior or introduce a new vulnerability.
- A patch author needs concrete failures and coverage gaps before another revision.
When NOT to Use
- No patch exists yet; use vulnerability discovery or fix implementation first.
- The task is to review an audit finding against a report without executing patch evidence.
- The task is only to convert a finding into a permanent project test.
- The target is remote or production. This skill executes local code and tests only.
- The user has not authorized execution of the repository's code or test suite.
Quick Start
-
Pin the vulnerable base and patched input. Prefer immutable commits. For uncommitted work, create a binary patch file first; do not validate in the user's working tree.
-
Scaffold a pinned plan:
uv run {baseDir}/scripts/post_patch_validation.py scaffold \ --repo . \ --base-ref <vulnerable-ref> \ --patched-ref <patched-ref> \ --finding-id <stable-id> \ --finding-summary "<root cause and impact>" \ --evidence-level runtime \ --output post-patch-validation/plan.jsonUse
--patch-file <path>instead of--patched-reffor a patch artifact. Choose the highest honest evidence level:sourcefor source/patch invariants only,buildwhen target code is compiled or analyzed but the reported behavior is not executed, orruntimewhen the checks execute the reported behavior and its safety assertions. -
Inspect the finding, diff, callers, sibling paths, cleanup/error paths, and existing tests. Populate
checksin the generated plan. Runprint-schemafor the structural schema:uv run {baseDir}/scripts/post_patch_validation.py print-schema -
Run
validate-planfor the complete validation, including coverage, command restrictions, and pinned inputs, before executing code:uv run {baseDir}/scripts/post_patch_validation.py validate-plan \ --plan post-patch-validation/plan.json -
Execute the evidence plan:
uv run {baseDir}/scripts/post_patch_validation.py run \ --plan post-patch-validation/plan.json \ --output post-patch-validation/results -
Report
result.json,report.md, the evidence level, and the completeassessment. Return each finding to the patch author with its check ID, assertion, and saved logs. Identify each validation gap separately, including gaps that coexist with supported findings. After the author revises the patch, pin the new inputs and save a fresh validation run. Preserve the prior evidence. Passing supplied checks still requires human review before acceptance.
Evidence Contract
The runner rejects incomplete plans. Supply at least one check of every kind:
| Kind | Required observation |
|---|---|
control |
Benign harness succeeds on both base and patch |
exploit |
Original safety assertion fails on base and succeeds on patch |
variant |
A distinct root-cause variant fails on base and succeeds on patch |
behavior |
Unaffected behavior succeeds with byte-identical selected output |
regression |
Targeted non-security regression check succeeds on both revisions |
security |
Adjacent/new-vulnerability check succeeds on base and patch |
suite |
Existing project suite, sanitizer, or deterministic fuzz campaign succeeds on patch |
Commands are argv arrays, never shell strings. Put complex setup in a checked-in or plan artifact
script and invoke it with {plan_dir}. The runner fixes locale/timezone/hash-seed inputs, executes
checks in lexical ID order, records raw stdout/stderr, and never edits the original worktree.
Each check's timeout_seconds defaults to 300 and accepts integers from 1 through 3600.
Exceeding the timeout leaves a validation gap. A timeout alone does not establish a regression.
Every plan also contains a sorted submodules array ([] when none). Scaffolding infers affected
Gitlinks from the changed-file inventory. The runner initializes those pinned commits from the
source repository's existing Git module objects, never from .gitmodules network URLs; initialize
or fetch them in the source repository before validation.
Exploit and variant checks must prove they ran
A nonzero exit does not mean the vulnerability reproduced. An import error, a failed build, a
missing dependency, and a failed safety assertion all exit nonzero and are indistinguishable to the
runner. Every exploit and variant check must print and flush PPV_REACHED immediately
before it evaluates its assertion, on both revisions:
"argv": ["python3", "-c", "import app; value = app.render('<'); print('PPV_REACHED', flush=True); assert value == '<'"]
The token is also in the environment as PPV_REACHED_MARKER. It must land on stdout, as a line
of its own. Stderr is not scanned, because a Python SyntaxError traceback echoes the offending
source and would otherwise satisfy the check for a harness that executed nothing. A run without it
leaves a marker_missing gap. Independent findings from other checks remain in the result.
Flush explicitly: a harness whose payload segfaults or calls _exit loses buffered output and forfeits its own evidence.
These checks also run side-blind. {side} is not expanded for them, PPV_SIDE is absent from
their environment, the checkout directory is randomly named, and the plan validator rejects any
exploit or variant check whose argv or env mentions either. An assertion that can see which
revision it is on can assert on that instead of on the code, which is the cheapest possible way
to fake a reproduction followed by a fix.
Environment
Checks run under a fixed minimal environment: PATH, HOME, and a handful of temp/user keys,
plus LANG/LC_ALL=C, TZ=UTC, PYTHONHASHSEED=0, NO_COLOR, TERM=dumb. Everything else in
the caller's environment is dropped. Toolchains that need more get it explicitly:
uv run {baseDir}/scripts/post_patch_validation.py run \
--plan post-patch-validation/plan.json \
--output post-patch-validation/results \
--allow-env JAVA_HOME --allow-env CARGO_HOME
Forwarded names and values are recorded in result.json. A requested variable that is unset is an
error, not an empty string. Two classes are refused outright: names that read as credentials
(*SECRET*, *TOKEN*, *API_KEY*, …), because the value would be written into the result; and
names that change what executes (LD_PRELOAD, BASH_ENV, NODE_OPTIONS, GIT_SSH_COMMAND, …),
because those variables can change which code executes.
The runner's fixed variables and every PPV_* name are also reserved and cannot be forwarded.
Placeholders expanded in argv and per-check env values: {checkout} (the revision under test),
{plan_dir} (an isolated copy of the plan artifacts for that one invocation), {scratch} (a
fresh opaque directory for that one check invocation), and
{side} (base or patched, and not available to exploit/variant checks). The same values
arrive as PPV_CHECKOUT, PPV_PLAN_DIR, PPV_SCRATCH, PPV_SIDE, and PPV_CASE_ID. Write only
under {scratch}; the evidence directory path is not passed to checks. Base and patched invocations
do not share runner-managed scratch, plan, or worktree roots. After each invocation exits, its
scratch tree is archived under the deterministic results/scratch/<check-id-and-side> path, its
private plan copy is discarded, and every readable argv element that resolves to a file is hashed
in argv_files. Files inside the isolated plan or checkout roots are additionally retained under
results/helpers/<sha256> up to 16 MiB; the record explains why any other file was not archived.
Use a dedicated directory for plan.json: its sibling files and directories are copied into each
invocation's {plan_dir}. Keep helper code under that directory's checks/ directory or checked
into the target repository so its bytes are reviewable. The machine plan containing commit pins,
the current output directory, and detected prior result trees are excluded; symlinks are rejected.
The clean snapshot remains only in runner memory, and
exploit/variant sides execute in random order while evidence filenames remain deterministic.
Stdout/stderr use anonymous or randomly named capture descriptors and are copied to the named
evidence files only after the child exits, so fd inspection cannot disclose the side label.
This isolation is not a host sandbox: checks run with the caller's privileges and a malicious helper could use arbitrary external state or deliberately infer the revision from source or Git metadata. Inspect the content-addressed helper artifacts, and use an OS/container sandbox when the check code itself is untrusted.
Active validation worktrees are Git-locked with random owner tokens backed by kernel file locks, so
another concurrent validator cannot prune them and PID reuse cannot impersonate an owner. If the
runner is forcibly killed, the next run unlocks stale validator-owned registrations. For manual
recovery, inspect git worktree list, then use git worktree unlock <path> and
git worktree remove --force <path> (or git worktree prune after the path is gone).
Read evidence-model.md when designing coverage, selecting variants, or interpreting findings and validation gaps. Do not read it for routine CLI execution.
Coverage Rules
- Derive variants from the root cause, not cosmetic mutations of the original payload.
- Enumerate sibling call sites, alternate callbacks/outputs, error paths, teardown, ownership, serialization, and boundary values touched by the fix.
- Make each exploit or variant test assert the safe behavior. It must fail on the vulnerable base; a test that passes on both revisions proves nothing about remediation. Read the base-side stderr and confirm the failure is the assertion you wrote, not a harness that never got there.
- Keep exploit and variant assertions limited to the security invariant. Test liveness, exact
error types/messages, timing, and compatibility separately as
behaviororregressionchecks; otherwise an unrelated contract change can masquerade as proof that the vulnerability remains. - Keep the
controlharness benign and make it exercise the changed component. It establishes that the harness works on both revisions. Failed controls leave gaps and prevent attributing other failures to the patch. The raw observations remain available for review. - Use
behavioronly for behavior that should remain unchanged. Exact output comparison is deliberate; move unstable values behind a deterministic test harness instead of normalizing them away in prose. - Make
securitychecks pass on the vulnerable base before treating a patched failure as newly introduced. A failed baseline leaves attribution unresolved. - Do not edit the patch during validation. Return failures to the patch author and start a new, freshly pinned run.
Reading the result
result.json schema 2.0 contains an assessment with status, findings, gaps, and
human_review_required. Status is complete when all required checks produced usable evidence,
even if some checks found failures. Status is incomplete when any gap remains. Findings name the
check ID, check kind, and failed expectation. Gaps name the check ID and missing evidence, with a
null check ID for run-level problems such as cleanup failures.
Suite checks run on the patched revision first. A completed failure triggers the same check on baseline. If baseline passes, report the failure after the patch. If both fail, preserve both logs and report that attribution is unresolved. Do not assume matching exit codes mean the same failure.
The runner exits 0 for complete checks with no findings, 1 for complete checks with findings, 10 for incomplete validation, and 64 for invalid inputs. Read the artifact even after exit 10: it can contain supported findings alongside gaps. Source or build evidence cannot establish runtime behavior. State the evidence level alongside any passing result.
Claude Dynamic Workflow
Claude Code exposes the bundled workflow as /post-patch-validation:validate-patch.
To pass structured inputs through the Workflow tool, use the name without a leading slash:
Workflow({
name: 'post-patch-validation:validate-patch',
args: {
finding: '<finding text or local path>',
baseRef: '<vulnerable-ref>',
patchRef: '<patched-ref>',
workdir: 'post-patch-validation',
},
})
Use patchFile instead of patchRef when appropriate. The workflow uses fixed coverage
lenses to propose checks and a fixed executor to run this skill. Agents may author test
artifacts. The Python runner records findings and gaps, and reviewers report coverage or evidence
concerns separately. NEEDS_REPAIR returns supported failures even when other checks left gaps.
BLOCKED means evidence is incomplete without a supported failure. Passing checks advance to
READY_FOR_HUMAN_REVIEW only after both evidence reviews approve, otherwise REVIEW_REQUIRED.
The workflow cannot ask questions after launch, so pass every input up front.
Rationalizations to Reject
| Rationalization | Required response |
|---|---|
| "The original PoC no longer works" | Test at least one independent root-cause variant |
| "The exploit failed on base, so it reproduced" | Confirm the marker and that the failure is the assertion, not a broken harness |
| "The full suite passes" | Prove baseline reproduction and targeted behavior explicitly |
| "This matches the upstream/canonical patch" | Treat provenance as context, not evidence |
| "The diff is tiny" | Exercise callers, failure paths, and teardown affected by the change |
| "All supplied checks passed" | Preserve artifacts and require human review |
| "A flaky rerun passed" | Keep the first pinned result; fix nondeterminism before retrying |
| "There is no obvious variant" | Inspect sibling sites and boundaries; otherwise report the missing coverage |
Archivos de esta skill
5Preguntas sobre la skill post-patch-validation
¿Cómo instalo la skill post-patch-validation en Claude Code?
Ejecuta npx degit trailofbits/skills/plugins/post-patch-validation/skills/post-patch-validation ~/.claude/skills/post-patch-validation. Claude Code carga las skills desde ~/.claude/skills (todos los proyectos) o .claude/skills (un proyecto) y usa una skill cuando su descripción coincide con la tarea.
¿Qué clientes pueden usar la skill post-patch-validation?
Cualquier cliente que lea el formato Agent Skills: Claude Code, Codex, Gemini CLI y claude.ai (subir como ZIP). Los scripts de la skill se ejecutan solo donde el cliente permite la ejecución de código.
¿Cuándo debería usar la skill de post-patch-validation?
Úsala cuando exista un parche de seguridad, un commit de remediación o un parche generado por IA que necesite validarse contra el error original, posibles variantes o nuevas regresiones.
¿Cuáles son los diferentes niveles de evidencia disponibles?
La skill admite tres niveles: 'source' para invariantes, 'build' para código compilado o analizado sin ejecución, y 'runtime' para ejecutar el comportamiento reportado y las aserciones de seguridad.
¿Cómo puedo asegurarme de que una comprobación de exploit realmente llegó a la vulnerabilidad?
Cada comprobación de exploit y variante debe imprimir y limpiar el token 'PPV_REACHED' en stdout inmediatamente antes de evaluar su aserción para demostrar que se ejecutó la ruta de código.
¿Es seguro ejecutar esta skill en entornos de producción?
No, esta skill está diseñada para ejecutar únicamente código y pruebas locales; no debe utilizarse en objetivos remotos o de producción.