Directives Toolkit

Audit current repo for drift between directive files and actual code, a full recursive code-correctness sweep, and structural soundness — always weighing whether re-organizing files would make the layout clearer and more error-proof

Lock answers to Chromebook browser-only constraints

Manual backup trigger for the pre-push verification directive (run tests, lint, CI checks before committing)

Run a command against any public GitHub repo via gh api — inspect, compare, or audit without cloning

Full environment readiness check — session context, git health, CI status, validation gates, directive freshness, a connectors/tools inventory, and the scope.chk repo-scope verification

Independent code quality reviewer for changed files. Use before PR or merge to assess maintainability, architecture, readability, tests, and implementation risk. This agent must not rewrite code unless explicitly asked.

Final PR readiness gate. Use after implementation, verification, review, and fixes to confirm tests, lint/build, required reports, unresolved issues, and CI readiness before opening or merging a PR.

Runs the full QA pipeline in sequence — test-verifier, ui-tester, code-reviewer, security-reviewer (if relevant), and pr-readiness-reviewer. Orchestrates a feedback loop with ui-tester until all UI scenarios pass or human escalation is required.

Security-focused reviewer for code changes. Use for features touching auth, user input, data access, file handling, secrets, dependencies, infrastructure, or sensitive data. This agent must not modify code unless explicitly asked.

Focused Supabase specialist. Use to apply schema migrations via Supabase MCP, query tables and verify row counts, inspect RLS policies, run the project's scheduled data script manually, and validate that Supabase secrets/variables are correctly configured. Follows the data directive — RLS always on, service-role key server-side only.

Use whenever asked to compare two documents: produce a self-contained side-by-side HTML diff (strikethrough deletions, red-underline additions, margin notes only for substantive changes).

Use BEFORE discussing, offering, or promising work on any repository other than the one this session is scoped to. Verifies the session's TRUE repo scope (GitHub MCP scope, add_repo/list_repos availability) so cross-repo access is never overclaimed.

Standard procedure for ANY change that updates a GitHub Pages site. Use AUTOMATICALLY whenever an edit touches a Pages-served file (root index.html, docs/*.html, served CSS/assets) or Pages config: run gates, push, watch the deploy to a terminal state, and report live/stuck/failed proactively.

3 hooks across 2 events