Periodic judgment sweep for doc drift a check can't catch (files issues, no edits)

Abierto
  • ¿Algo no está bien?
#7,628 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
devtools, documentation

Línea de trabajo

Read #7624 and #7617 first to understand the existing audit and parallel read-only approach. Compare the procedures in .claude/skills, .claude/rules, .claude/agents and docs/agents with the workflows and tools, then check README and docs/validation.md claims against cited evidence and dates. Document the doc groups, comparison list, and issue format in a skill or docs/agents/ page; done when the first run files findings with both sides and file:line references.

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

Descripción

documentation

Part of #7624 (step 5).

About 20% of the drift in #7617 needed judgment no check can supply:

  • CLAUDE.md still described a removed PR trigger on the full-suite matrix (#4518).
  • Three skills told agents to call update_golden_master.py directly, against golden-master-guidelines.md.
  • The tri-comparison figures (200/201, 2026-08-30) had not been re-audited.
  • Procedures conflicted: a rebase with --force-with-lease vs. "never rebase".

Change: a monthly sweep, or one before each release tag, by an agent run. It compares:

  1. procedures in .claude/skills, .claude/rules, .claude/agents and docs/agents against the workflows and tools they describe (triggers, required steps, the bless path);
  2. README and docs/validation.md claims against their cited evidence, with dates;
  3. contradictions between docs.

It files issues and never edits files, because most of these fixes need an owner decision. Each issue names both sides, with file:line references. Parallel read-only agents, one per doc group, as in #7617, keep the cost down; the doc-refs audit has already removed the mechanical half.

Acceptance: a documented runbook (a skill or a docs/agents/ page) with the doc groups, the comparison list and the issue format. The first run files its findings.

Lenguaje dominante
Python
Estrellas
57
Forks
11
Merge medio
1 h 35 min
PR fusionados (30 d)
975

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 squid-protocol/gitgalaxy

Todos los issues de squid-protocol/gitgalaxy

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.