By name: 400-sf-audit description: "Audit product, code, design, SEO, GTM, and performance." argument-hint: '[file-path | "global"] (omit for full project)'
Canonical Paths
Before resolving any ShipFlow-owned file, load $SHIPFLOW_ROOT/skills/references/canonical-paths.md ($SHIPFLOW_ROOT defaults to $HOME/shipflow). ShipFlow tools, shared references, skill-local references/*, templates, workflow docs, and internal scripts must resolve from $SHIPFLOW_ROOT, not from the project repo where the skill is running. Project artifacts and source files still resolve from the current project root unless explicitly stated otherwise.
Instruction Layering
This SKILL.md is the activation contract. Before editing or expanding this skill, load $SHIPFLOW_ROOT/skills/references/skill-instruction-layering.md and keep bulky workflow detail in skill-local references.
Chantier Tracking
Trace category: conditionnel.
Process role: source-de-chantier.
Before producing the final report, load $SHIPFLOW_ROOT/skills/references/chantier-tracking.md. If attached to one unique chantier spec, write the run trace there. If no unique chantier exists, do not write to a spec.
Chantier Potential Intake
Because this skill has process role source-de-chantier, evaluate the standard threshold from $SHIPFLOW_ROOT/skills/references/chantier-tracking.md before the final report. Add a Chantier potentiel block when findings reveal non-trivial future work and no unique chantier owns it.
Report Modes
Before producing the final report, load $SHIPFLOW_ROOT/skills/references/reporting-contract.md.
Default to report=user: concise, findings-first for audits and failures, outcome-first for successful support runs, and in the user's active language. Use report=agent, handoff, verbose, or full-report only when detailed evidence is needed.
Required References
Always load shared references only when their gate applies. Load skill-local references precisely by mode:
references/audit-master-workflow.md: Master audit planning, domain routing, parallel/read-only audit rules, consolidation, tracking, and fix handoff details.$SHIPFLOW_ROOT/skills/references/operational-record-format.md: required before creating or mutating audit or task operational records inAUDIT_LOG.mdorTASKS.md.
Mode Detection
Parse $ARGUMENTS and choose the smallest safe mode under $SHIPFLOW_ROOT/skills/references/decision-quality-contract.md: bounded professional scope, never shortcut quality.
- GLOBAL MODE: load
references/audit-master-workflow.mdto plan and coordinate cross-domain or cross-project audits. - PROJECT MODE: load
references/audit-master-workflow.mdbefore launching domain audits, consolidation, or fix handoffs. - Use specialist
400-sf-audit-*skills directly when one domain is obvious.
Core Execution Rules
- Findings first; prioritize cross-domain P1/P2 clusters and systemic risk.
- For projects with UI, treat missing or bypassed design-system authority as a systemic design/governance risk and ensure the Design lane checks
skills/references/design-system-token-contract.md. - Evaluate
Chantier potentielwhen findings require multi-domain remediation, staged fixes, or owner-skill follow-up. - Use bounded read-only audit fan-out only when each lane has disjoint evidence scope and no file mutation.
Stop Conditions
Stop and report blocked when:
- A required reference is missing or contradicts this activation contract.
- The requested work would change behavior outside this skill's scope.
- A safety, security, documentation, source, claim, auth, production, redaction, or chantier guardrail would need to be weakened.
- The action would edit unrelated dirty files or mutate durable state without an owner-skill contract.
Validation
Validate this skill after edits with:
rg -n "Trace category|Process role|Chantier Potential|Report Modes|GLOBAL MODE|PROJECT MODE|findings|parallel|references/" skills/400-sf-audit/SKILL.mdpython3 tools/skill_budget_audit.py --skills-root skills --format markdowntools/shipflow_sync_skills.sh --check --all