skills.rest
ajbarea
ajbareaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

audit

Validate repository make targets against timestamped dev-run log archives.

Updated May 2, 2026
Search Tags:#makefile#build verification#repo hygiene#ci readiness#log reconciliation#lint tests#dev-run archives
One-click install
npx skills add https://github.com/ajbarea/techne --skill audit-ajbarea
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/ajbarea/techne/tree/main/plugins/techne/skills/audit
Command: npx skills add https://github.com/ajbarea/techne --skill audit-ajbarea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you confirm whether your repository’s build, lint, tests, and end-to-end checks are genuinely clean by reconciling what you ran in the terminal against the recorded dev-run log archives.

Core Features & Use Cases

  • Make-phase audit in dependency order: Runs setup → lint → test → end-to-end as a structured sequence so downstream phases build on earlier artifacts and logs.
  • Archive-based verification: Checks that each command’s terminal exit code matches the newest timestamped log archive and its SUMMARY block.
  • Full vs fast audit modes: Supports a complete validation pass or a quick “ready to push” lint+test style probe.
  • Noise hunting via log sweep: Greps the fresh archives for error markers to surface failures and tracebacks for triage.

Quick Start

Ask to run the full audit to reconcile your latest make output against the logs/dev-*.log archives and get a pass/fail matrix.

Frequently Asked Questions about audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify make build targets against timestamped dev-run log archives?▼

You can validate CI readiness by running a fast audit mode that probes lint and test phases, stops early at setup failures, and cross-checks exit codes against timestamped dev-run log archives for a quick pre-push confidence check.

What is the difference between full and fast audit modes for makefile verification?▼

Full audit mode runs a complete validation pass across all make phases from setup to end-to-end, while fast mode performs a quick lint and test probe with stop-early behavior to quickly assess if your repository is ready to push.

Do I need timestamped log archives under logs/ to run make target verification?▼

Yes, timestamped log archives globbed under logs/ are required. The audit extracts exit code and SUMMARY fields from the newest logs/dev-<ts>-<cmd>.log archive to reconcile terminal results, and it never reads logs/dev-latest.log.

How do I hunt for errors and tracebacks in make build logs before pushing?▼

To hunt for build log errors, the audit performs a log sweep that greps fresh timestamped archives under logs/ for error markers, surfacing failures and tracebacks for triage during your pre-push lint and test verification workflow.

Why should I reconcile terminal make output with dev-run log archives instead of just checking exit codes?▼

Reconciling terminal make output with dev-run log archives confirms that your build, lint, and test checks are genuinely clean by matching terminal exit codes against recorded SUMMARY blocks, ensuring deterministic CI-confidence workflows rely on verified log conventions.

Related Skills

Explore More Software Engineering Skills→
merongmerong

save-conversation

Summarize conversations into timestamped Markdown logs under conv-logs.

Community
Intermediate
mlinnenmlinnen
1

release-validation-triage

Triage release readiness by re-running failing tests in isolation.

Community
Intermediate
open-haxopen-hax
6

giga-workflow

Watch submodule changes and run tests, builds, or lint targets.

Official
Advanced
RDEWAIRDEWAI
5

update-pipeline

Modify CI/CD pipeline configurations incrementally while preserving existing deployment workflows.

Official
Advanced