audit

Dumps full crosslink project context including session state, issues, locks, and git status for re-orientation.

1.4k|335|Updated Jun 10, 2014
One-click install
npx skills add https://github.com/openwpm/OpenWPM --skill audit-openwpm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/openwpm/OpenWPM/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/openwpm/OpenWPM --skill audit-openwpm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working in a crosslink-tracked project, it is easy to lose track of what issue is active, what state the repository is in, and what blockers exist. This Skill performs a full context dump so you can re-orient and decide your next action based on real data instead of guesses. ## Core Features & Use Cases - Full State Inspection: Reads project rules, session state, active issue details, blockers, locks, hook configuration, and VCS state in one structured pass. - Diagnostic Summary: Prints a consolidated summary covering session, change, tracking mode, languages, open issues, locks, and uncommitted changes. - Use Case: You return to a project after a break and cannot remember what you were doing. Run the audit to see the active issue, its comments, any blocking dependencies, and the current jj working-copy state before deciding what to do next. ## Quick Start Tell the assistant you are stuck or ask for an audit so it dumps the full crosslink project context and suggests a next action.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I re-orient myself in a crosslink-tracked project?

Run the audit workflow, which reads project rules, checks session status with crosslink session status, shows the active issue, lists blockers and locks, and prints a diagnostic summary so you can decide your next action.

What information does a crosslink audit collect?

It collects project rules, dependency versions, session state, active issue details and comments, blocked and ready issues, lock state, hook configuration, and jj working-copy status, then prints a consolidated summary.

Does the audit skill work without the crosslink CLI installed?

No. The audit relies on crosslink commands such as session status, issue show, locks list, and config show, plus jj for VCS state. Without these tools installed and a .crosslink directory present, the audit cannot gather state.

When should I run an audit instead of just continuing work?

Run an audit when you are stuck, confused, or returning after a break and cannot recall the active issue or repository state. It is designed for re-orientation, not for routine task execution.

Why does the audit check locks and blocked issues?

Locks indicate issues held by other agents, and blocked issues reveal dependency constraints. Checking both prevents you from starting work that is already claimed or cannot proceed yet.