Audit recent Git commits for CLAUDE.md convention compliance.
npx skills add https://github.com/victoriacity/openakari --skill self-audit
Please help me install this Agent Skill. Skill: self-audit Source: https://github.com/victoriacity/openakari/tree/main/.claude/skills/self-audit Command: npx skills add https://github.com/victoriacity/openakari --skill self-audit
This Skill automatically checks your recent code commits and session work against established conventions, ensuring adherence to logging standards, experiment validation, and overall workflow hygiene.
CLAUDE.md guidelines, including log entry completeness, inline logging discipline, and findings provenance.Run a self-audit of the last session's work for convention compliance.
High-intent search queries and answers about installing and using this skill.
To check recent git commits for convention compliance, you audit committed code history within a specified time range to identify violations in log completeness, inline logging, and findings provenance. This ensures adherence to established CLAUDE.md guidelines.
Session validation in code workflow hygiene is the process of auditing recent session work to verify compliance with log entry standards and experiment validation. It analyzes committed code history to identify deviations from task lifecycle and budget adherence rules.
Yes, you need Git for history traversal and file parsing to audit task lifecycle tags, experiment records, and decision debt. The audit requires traversing commit history to check for convention violations and archive thresholds.
You scan code history for decision debt and budget adherence issues by analyzing committed work within a specific time range against CLAUDE.md conventions. This process identifies violations in task lifecycle tags, experiment records, and cross-referencing.
The best way to automate convention checks before merging is to scan the last few days of commits to identify deviations from coding and documentation standards. This verifies log entry completeness, inline logging discipline, and findings provenance automatically.
Yes, you can audit experiment validation and archive thresholds without a dedicated linter by parsing files directly from Git history. This approach checks for convention violations, cross-referencing issues, and decision debt using standard history traversal.
Mr-Fang-VLSICommit and tag git changes while logging human-readable version entries.
oletiziCopy baked feature-image assets into a blog post's public directory and update frontmatter.
ManfronEnricoBlock merges when high-severity workspace violations lack waivers.
pkuppensRun lint, format, type checks, and security scans on every commit.