doc-bug-auditor

Auditing project status involves reading repository state, logs, and test outputs to classify failures and blockers. The Skill examines astro state files like tasks.md and status.md to generate a structured audit with recommended next actions.

Diagnosing project completion requires examining repository state, test outputs, and traceback information. The audit classifies tasks across astro components as finished, in progress, blocked, or failing, using evidence from logs and version information.

Yes, test outputs, logs, and traceback information are used to classify project failures and blockers. The audit reads this evidence alongside repository state and version information to determine what is blocked or failing and recommend next actions.

Summarizing completed work and in-progress tasks is done by auditing the project directory using repository state and optional astro state files like tasks.md and status.md. This generates a concise status report with evidence-driven conclusions.

Yes, the project audit reads optional astro state files such as astro/tasks.md and astro/status.md when present. These files provide evidence to assess completion status and blockers across astro components and tasks.

When project blockers are not showing up, ensure the audit examines repository state, logs, and test outputs for traceback and version information. The audit uses this evidence to classify failures and recommend structured next actions.