Menu
Check a project repo against workspace and project-level conventions. Reports governance coverage, documentation gaps, and test status.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | audit-project |
| description | Check a project repo against workspace and project-level conventions. Reports governance coverage, documentation gaps, and test status. |
/audit-project [<repo-name>]
If no repo name is given, audit the project repo in the current directory (when working in a layer worktree).
Lifecycle position: Utility/periodic — run before or after repo work to check project-level governance. Not tied to the per-issue lifecycle.
Check a project repo against workspace standards and its own governance docs. Reports what's present, what's missing, and what may have drifted. Useful for onboarding to a repo, identifying documentation gaps, or verifying governance adoption.
Not the same as audit-workspace — that checks workspace-level governance.
This checks a single project repo.
If a repo name is given, find it under layers/main/*/src/<repo-name>.
If not, use the current directory. Verify it's a valid project repo
(has at least one package.xml).
# Find repo location
find layers/main/*/src/<repo-name> -maxdepth 0 -type d 2>/dev/null
Using the governance template (.agent/templates/project_governance.md)
as reference, check what exists:
| Item | Status | Path |
|---|---|---|
.agents/README.md | Present / Missing | ... |
PRINCIPLES.md | Present / Missing | ... |
ARCHITECTURE.md | Present / Missing | ... |
docs/decisions/ | Present / Missing (N ADRs) | ... |
.agents/workspace-context/ | Present / Missing | ... |
This is a coverage report, not a mandate — not every repo needs full governance. But missing items should be noted.
If .agents/README.md exists, check it against the template
(.agent/templates/project_agents_guide.md):
package.xml files?For each package.xml in the repo:
For each package:
test/, tests/, *_test.py, *_test.cpp)# setup.bash must be sourced in the same shell — agents run each command in a fresh subprocess
source .agent/scripts/setup.bash && cd layers/main/<layer>_ws && colcon test --packages-select <package> && colcon test-result --verbose
Report test existence and pass/fail, not test quality.
README.md exist?.repos config file?.agent/project_knowledge/ symlink (pointing to
.agents/workspace-context/) include content from this repo?## Project Audit: <repo-name>
**Location**: `layers/main/<layer>_ws/src/<repo-name>`
**Packages**: N packages (list)
### Governance Coverage
| Item | Status |
|---|---|
| `.agents/README.md` | Present / Missing |
| `PRINCIPLES.md` | Present / Missing |
| ... | ... |
### Agent Guide
<findings if .agents/README.md exists, or "No agent guide — consider
creating one with the project_agents_guide.md template">
### Package Metadata
| Package | Description | License | Maintainer | Tests |
|---|---|---|---|---|
| `pkg_name` | OK / Missing | OK / Missing | OK / Missing | Exist / Missing |
### Documentation
| Item | Status |
|---|---|
| Top-level README | Present / Missing |
| ... | ... |
### Workspace Integration
| Check | Status |
|---|---|
| Listed in .repos | Yes / No |
| Correct layer | Yes / No |
| ... | ... |
### Recommended Actions
- [ ] <specific action items>
Host orchestrator that drives an issue through the full per-issue lifecycle — dispatches each phase (review-issue → plan-task → review-plan → implement → review-code → triage-reviews → address-findings) as a fresh-context sub-agent, reads each phase's progress.md entry to choose the next action, and pauses at user checkpoints. Local-first: the PR is created at the end, never auto-pushes or auto-merges without confirmation.
Evaluate a GitHub issue against workspace principles and ADRs before work begins. Records findings in progress.md and best-effort posts them as a comment on the issue.
Independent evaluation of a committed work plan before implementation begins. Checks scope, approach, principle alignment, consequences, and ROS conventions.
Activate deployment mode for a live field deployment. Discovers the project's deployment config, detects dev/field side via field_mode.sh, and either creates a new deployment, first-activates an existing one (worktree/main-tree + per-host log + issue-sync push), or resumes an ongoing one. Loads the urgency contract (sterile-cockpit / mitigate-before-diagnose / time-box) into the current agent session.
Close out a field deployment. Verifies dev-side access, finds the open deployment issue, collects field logs, interviews the operator for corrections, consolidates the dev log, reconciles field code via SHA-preserving merge and /import-field-changes, opens the wrap-up PR (Closes
Lead reviewer that orchestrates specialist sub-reviews (static analysis, governance, plan drift, adversarial) to evaluate a PR or pre-push diff. Scales review depth to change risk. Produces a unified structured report and persists findings to progress.md.