agentsclimarketplace
Sign in

Create audit

Skill jkaloger/lazyspec/skills/create-audit

Use when running a criteria-based review (health check, security audit, accessibility review, pen test, bug bash, spec compliance). Creates an Audit document with findings and presents them to the user for triage.From its SKILL.md

Install
npx -y skills add jkaloger/lazyspec --skill create-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, as published. Nobody here has run it

AUDITS DOCUMENT FINDINGS. THEY DON'T FIX THEM.

Present findings to the user. Let them decide what to act on.

<HARD-GATE> Do NOT create iterations from findings. The audit produces a findings report that the user triages. Only after the user selects findings to act on should `/lazy` be used to author a delivery document for them, and that is a separate skill invocation. </HARD-GATE> <NEVER> - Do NOT write document files directly. Use `lazyspec create` and `lazyspec link`. - Do NOT edit a document you haven't read. Always `lazyspec show <id> --json` or `Read` first. - Do NOT create iterations from audit findings. Present findings to the user for triage. - Do NOT fix issues found during the audit. Document them only. </NEVER> <GITHUB-ISSUES-DOCUMENTS> Documents stored in GitHub Issues (store = "github-issues") are managed through the GitHub API. The `.lazyspec/cache/` directory contains read-only mirrors. - Never edit files under `.lazyspec/cache/`. Use `lazyspec update <ID> --body` to modify content. - Always use shorthand IDs (e.g. STORY-095) not cache file paths when referencing documents in `lazyspec link`, `lazyspec update`, `lazyspec show`, etc. - To set body content at creation: `lazyspec create <type> <title> --body "content"`. - To modify after creation: `lazyspec update <ID> --body "new content"`. </GITHUB-ISSUES-DOCUMENTS>

Always run lazyspec help <subcommand> before using unfamiliar commands. Always pass --json. On failure, check --help before retrying.

Workflow

Define scope and criteria -> Create audit doc -> Review codebase -> Document findings -> Validate -> Present to user

Present to user -> User triages findings -> Use /lazy skill: for selected findings

Present to user.shape: diamond
Use /lazy skill.shape: double_circle

Steps

  1. Define scope and criteria with the user.
  2. Check for existing audits: lazyspec search "<topic>" --json
  3. Create: lazyspec create audit "<title>" --author <name>
  4. Link: lazyspec link <audit-path> related-to <target-path> for every document the audit references.
  5. Review codebase: Use Explore subagents (Sonnet) per area or criterion.
  6. Document findings in the audit. Each finding must have:
    • Severity: critical, high, medium, low, or info
    • Location: file path or component
    • Description: what was found
    • Recommendation: what should be done
  7. Validate: lazyspec validate --json
  8. Present findings to user grouped by severity. Do NOT create iterations.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.