pre-audit-setup

Prepares a project for codebase audits by building a graphify knowledge graph and configuring hooks.

3|5|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill pre-audit-setup-bensheridanedwards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-audit-setup
Source: https://github.com/BenSheridanEdwards/ArchitectPlaybook/tree/main/pre-audit-setup
Command: npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill pre-audit-setup-bensheridanedwards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before running any codebase audit, the target project needs a knowledge graph, a configured PreToolUse hook, and a findings directory. Doing this setup manually is error-prone and easy to forget; this Skill performs the entire preparation idempotently in one pass. ## Core Features & Use Cases - Graphify verification and graph build: Confirms graphify is installed at ~/.claude/skills/graphify, then invokes /graphify to produce graphify-out/graph.json and GRAPH_REPORT.md as the map of the codebase. - Hook merging into .claude/settings.json: Adds a graphify-aware PreToolUse hook for Glob and Grep calls without duplicating entries or touching unrelated settings. - Findings directory scaffolding: Creates .architect-audits/ with a .gitkeep so downstream audits have a stable output location. - Use Case: After installing the architect-playbook skills on a new repository, run this once so that security, performance, and architecture audits can all read the same knowledge graph in parallel sessions. ## Quick Start Run /pre-audit-setup in the project root to verify graphify, build the knowledge graph, and configure the audit environment.

Frequently Asked Questions about pre-audit-setup

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

FAQPage Schema
How do I set up a project for codebase audits with graphify?

Run /pre-audit-setup once in the project root. It verifies graphify is installed, builds the knowledge graph with /graphify, merges the PreToolUse hook into .claude/settings.json, and creates the .architect-audits findings directory.

What does the pre-audit-setup skill do before running audits?

It performs one-time idempotent preparation: checking graphify presence, generating graphify-out/graph.json and GRAPH_REPORT.md, adding a graphify hint hook for Glob and Grep calls, and scaffolding the findings directory with a checklist report.

Can I re-run pre-audit-setup without breaking my settings?

Yes, the skill is idempotent. It never duplicates the hook entry, never overwrites the knowledge graph unless --force is passed, and preserves every other field in .claude/settings.json. Use --dry-run to preview changes.

Why does pre-audit-setup fail with graphify missing?

The skill requires graphify installed at ~/.claude/skills/graphify and does not install it itself. Install graphify first using the official integration instructions, then re-run the setup.

Does pre-audit-setup modify global Claude Code settings?

No, it only touches the project-local .claude/settings.json file. It never modifies ~/.claude/settings.json, never installs graphify, and never commits anything to git.

When should I re-run pre-audit-setup with --force?

Re-run with --force after a major refactor, after pulling a branch that significantly changes file layout, or after adding new top-level packages, so the knowledge graph is rebuilt and no longer stale.