Audit site navigation — find dead-end features, missing backlinks, and poor discoverability. Produces an improvement list, no code changes.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Audit every feature to verify it's reachable through obvious UI paths. Produces an improvement list — does NOT make changes.
| Severity | Meaning |
|---|---|
| SHOWSTOPPER | Feature only reachable by typing the URL directly. |
| POOR | Reachable but path is non-obvious, buried, or link text is unclear. |
| MISSING BACKLINK | No link from a listing/parent page to its detail/action page. |
| SUGGESTION | Works but could be improved (shortcut, breadcrumb, contextual button). |
Audit each route for the role that should use it. Hidden admin features are correct, not bugs.
| Role | Sees |
|---|---|
| Unauthenticated | Public pages (home, login) |
| Authenticated (no approval) | Membership gate (profile setup, consent) |
| Active member | Full member experience |
| Lead | Team admin for their teams |
| Board | Admin panel subset, member approval |
| Admin | Full admin panel, configuration |
Scan for all controller actions and Razor pages — URL, HTTP method, required auth, purpose.
Sources:
src/Humans.Web/Controllers/*.cs — [Route], [HttpGet], [HttpPost], [Authorize] attributessrc/Humans.Web/Pages/**/*.cshtml — Razor pagessrc/Humans.Web/Views/**/*.cshtml — MVC viewsFor each route, find inbound links in:
_Layout.cshtml, _AdminLayout.cshtml, sidebar partials<a>, asp-action, asp-controller, asp-page tag helpersFor each route determine:
Verify multi-step workflows have clear navigation: form submit lands somewhere useful, list action buttons are visible, success pages link back to the relevant list.
Output sections in order: Route Inventory (totals by role), then four issue tables (SHOWSTOPPERS / POOR Discoverability / MISSING BACKLINKS / SUGGESTIONS), each with columns: Route | Feature | Problem/Current Path | Suggested Fix. Close with a counts summary.
Present the report. Do NOT make code changes until the user approves specific items.
If $ARGUMENTS specifies a section, audit only that area:
all (default) — entire siteteams — team browsing, joining, team adminadmin — admin panel navigationprofile — profile, email, privacy, contact fieldsconsent — legal documents and consent flowgovernance — asociado application flowNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Check an externally created PR for coding rule violations against memory/INDEX.md atoms and docs/architecture/code-review-rules.md.
The English summary is being prepared. Showing the original description.
Two-phase memory hygiene. Phase 1: scan external Claude Code memory (~/.claude/projects/<slug>/memory/) for durable rules to migrate into the repo and entries already duplicated by repo atoms. Phase 2: audit in-repo memory/, CLAUDE.md, docs/architecture/, and docs/sections/ for dead links, duplication, drift, and bloat.
The English summary is being prepared. Showing the original description.
Review, repair and steward the nightly Codex debt-sweep PR (branch codex/daily-debt/<date>). Judges every commit GOOD / REPAIR / REVERT, triages the bot review findings through /fix, lands one round-1 commit, files follow-up issues, then stewards the PR itself with a 3-round ceiling. Run by the 08:00 UTC cloud routine; also '/debt-review', '/debt-review 1789'.
The English summary is being prepared. Showing the original description.
Autonomous themed tech-debt cleanup. Reads docs/architecture/debt-ledger.yml, rotates to the least-recently-served debt theme, works it for a time budget (default 2h) or until drained, opens one PR, and asks judgment questions inline at the end. Use for daily debt burndown without Peter pointing at a target: grandfathered analyzer rules, architecture-test baselines, obsolete-field reads, cross-section stitching.
The English summary is being prepared. Showing the original description.
Scrap and regenerate the in-flight EF migrations on the current branch as one consolidated migration. Use when migrations have accumulated mid-development cruft (added/removed columns, stacked add-column-to-existing-table fixes, hand-edited SQL that needs to come out, schema changes that should have been one migration but ended up as five), or when the branch has merged main and its migrations are now stuck mid-chain so `dotnet ef migrations remove` is unsafe. Triggers on phrases like 'regen the migrations', 'redo these migrations', 'scrap and regen migrations', 'consolidate the in-flight migrations', 'redo the migration stack', or any time an agent hits the mid-chain situation in `memory/architecture/migration-regen-after-rebase.md`.
The English summary is being prepared. Showing the original description.
Use when a sprint tracking issue (label `sprint`) on peterdrier/Humans needs working — routine-fired cloud runs, or any unattended session told to execute the sprint queue.
The English summary is being prepared. Showing the original description.