Audit Flush
Inspect and flush staged audit-trail entries to the remote trail repository. Use when the user asks to "flush audit trail", "show what's pending in audit trail", "dry-run audit flush", "retry audit pending", or when diagnosing why a previous auto-flush was skipped (secret hit, push failure, manual mode).
Install
$ agentstack add skill-levnas-ccaudit-audit-flush ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-levnas-ccaudit-audit-flush) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
audit-flush
Manual counterpart to the Stop hook. Same logic, invoked on demand.
When to use
- The user asks to inspect staged trail entries before they auto-flush.
- The user wants to retry entries that moved to
$CCAUDIT_PENDING_DIRafter an earlier failure (secret hit or push error). - Auto-flush is disabled (
CCAUDIT_MANUAL=1) and entries must be flushed explicitly. - The user needs a written record that " inspected and approved this flush at time X" — running
/audit-flushleaves a trace (the commit author and timestamp) that an unattended Stop hook cannot.
Flags
| Flag | Behavior | |------|----------| | (none) | Same flow as hooks/auto-flush.sh: scan, secret-check, push, clear staging. | | --dry-run | List what would be flushed, exit without touching anything. | | --force | Include $CCAUDIT_PENDING_DIR contents in addition to staging; retry everything. |
Procedure
Follow skills/audit-flush/procedure.md step by step. Do not invent additional safety checks — the hook and this skill must stay behavior-identical, so divergence creates undefined state.
What this skill does NOT do
- It does not modify trail entries. Entries are append-only once written to staging.
- It does not delete from the remote trail repository. If a bad entry was pushed, the correction is a new entry referring to the bad one by hash — never a rewrite.
- It does not reconfigure the remote.
CCAUDIT_TRAIL_REPOis read-only from this skill's perspective.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: LevNas
- Source: LevNas/ccaudit
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.