Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Send us a transcript where backcheck got it wrong

Abierto Apto para principiantes
  • ¿Algo no está bien?
#6 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
rust
Área
cli, testing-qa

Línea de trabajo

Comienza con el patrón relevante en src/claims.rs, especialmente is_hedged() y is_negated(), y luego reproduce el veredicto falso con un fixture JSONL mínimo y saneado en tests/fixtures/. Ejecuta backcheck -f your-fixture.jsonl --json y añade una prueba de regresión que muestre que la afirmación reportada se clasifica como se espera sin provocar coincidencias excesivas.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

accuracy false-negative false-positive help wanted

backcheck is only worth installing if you trust its verdicts. A hook that fires on honest work
gets uninstalled within a day, and then it protects nobody.

So the most valuable thing you can contribute is a case where it was wrong.

Two kinds of wrong

False positive — it flagged work that was fine. This is the expensive kind. Examples we
already fixed this way:

  • runners invoked through a virtualenv path (.venv/bin/python -m pytest) were invisible, so
    genuine runs looked like no run at all
  • the shell builtin test -f was counted as a test run, which could hide a missing suite
  • "Ruff passes with no warnings" was read as a negated sentence and skipped

False negative — an agent claimed something it had not done and backcheck stayed quiet.
Usually an unrecognised runner (#3) or a claim phrasing the patterns miss.

How to report one

Please do not attach a raw transcript. They contain your source, your paths, and sometimes
your credentials.

Send the smallest JSONL that reproduces it, with everything sensitive replaced. Three lines is
usually enough, and it can go straight into tests/fixtures/ as a regression test:

{"type":"assistant","message":{"content":[{"type":"tool_use","id":"t1","name":"Bash","input":{"command":"<command>"}}]}}
{"type":"user","toolUseResult":{"stdout":"<output>","stderr":"","interrupted":false},"message":{"content":[{"type":"tool_result","tool_use_id":"t1","content":"<output>"}]}}
{"type":"assistant","message":{"content":[{"type":"text","text":"<what the agent claimed>"}]}}

Then run backcheck -f your-fixture.jsonl --json and paste the output along with what you
expected instead.

There is an issue template for this: 🎯 Wrong verdict.

Claim phrasings we know are missed

Patterns live in src/claims.rs. Known gaps:

  • non-English summaries
  • emoji-only status (✅ tests with no verb)
  • markdown tables reporting per-check status
  • "everything is green", "CI is happy", "all clear"
  • claims about coverage thresholds
  • claims split across sentences ("Ran the suite. Everything passed.")

Each of those is a pattern plus a test, and the guard against over-matching is the interesting
part — see is_hedged() and is_negated().

Lenguaje dominante
Rust
Estrellas
1
Forks
2
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de VectorInstitute/backcheck

Todos los issues de VectorInstitute/backcheck

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.