ai-instructions: Skill for Cursor

Code Instruction Audit

Arguments

• Optional target path, module, file, or glob.
• Omit the filter to audit the full workspace.

1. Define the Scope

1. Load all instruction files applicable to the target scope from both:
   • the workspace directory .github/instructions/
   • the configured user-level directory ~/.agents/instructions/
2. Check each instruction file's applyTo pattern against the target files.
3. Treat both locations as active instruction sources. Do not ignore an applicable user-level instruction because it is outside the workspace.
4. If applicable instructions conflict, report the conflict and identify both sources. Stop rather than choosing a winner silently.
5. Resolve the target scope from the user-provided arguments when present. If missing, audit the full workspace.
6. Enumerate all code files in scope, sorted by path ascending.
7. Read each code file and check it against all applicable instructions.
8. If scope exceeds available context, process files in path order until context is exhausted, then set Verdict to CONTINUE and record the next unprocessed path.

Project decision records

1. Load project ADRs or equivalent decision records from the target workspace, typically under docs/adr/, when they exist.
2. Treat an ADR as an approved, project-specific exception only when all of the following are true:
   • its status is Accepted or equivalent;
   • it explicitly names the behavior, endpoint, component, or rule being decided;
   • the observed code is within the ADR's stated scope;
   • the ADR does not merely describe the current implementation.
3. An explicit accepted ADR may override a reusable instruction only for the narrowly described decision. Do not generalize the exception to unrelated code or rules.
4. Continue validating every non-exempt instruction and every compensating control described by the ADR.
5. Cite the ADR when suppressing a finding. If the ADR is ambiguous, obsolete, superseded, or broader than the observed decision, report the uncertainty and stop instead of silently accepting the exception.
6. Do not treat README text, comments, deployment assumptions, or undocumented conventions as equivalent to an accepted ADR.