backend-review
Review Go backend code for convention violations. Use after modifying files under components/backend/. Checks for panic usage,…
Review frontend TypeScript/React code for convention violations. Use after modifying files under components/frontend/src/. Checks for raw HTML elements, manual fetch, any types, interface usage, component size, and missing states.
$ npx -y skills add ambient-code/platform --agent claude-codeHow it fires
How this agent gets triggered: by you, by Claude, or both.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Review frontend TypeScript/React code for convention violations. Use after modifying files under components/frontend/src/. Checks for raw HTML elements, manual fetch, any types, interface usage, component size, and missing states.
name: frontend-review description: > Review frontend TypeScript/React code for convention violations. Use after modifying files under components/frontend/src/. Checks for raw HTML elements, manual fetch, any types, interface usage, component size, and missing states. tools: - Read - Grep - Glob - Bash
Review frontend code against documented conventions.
Load these files before running checks:
1. `specs/standards/frontend/conventions.spec.md` 2. `specs/standards/frontend/react-query.spec.md` 3. `components/frontend/DESIGN_GUIDELINES.md` (if it exists)
grep -rn "<button\|<input\|<select\|<dialog\|<textarea" components/frontend/src/ --include="*.tsx" | grep -v "components/ui/"
Must use Shadcn UI components from `@/components/ui/`.
grep -rn "fetch(" components/frontend/src/app/ components/frontend/src/components/ --include="*.tsx" --include="*.ts" | grep -v "src/app/api/"Use React Query hooks from `@/services/queries/`.
grep -rn "^export interface \|^interface " components/frontend/src/ --include="*.ts" --include="*.tsx" | grep -v "node_modules"
Use `type` instead of `interface`.
grep -rn ": any\b\|as any\b\|<any>" components/frontend/src/ --include="*.ts" --include="*.tsx" | grep -v "node_modules\|\.d\.ts"
Use proper types, `unknown`, or generic constraints.
find components/frontend/src/ -name "*.tsx" -print0 | xargs -0 wc -l | sort -rn | head -20
Flag components exceeding 200 lines. Consider splitting.
For components using `useQuery`:
grep -rl "useQuery\|useSessions\|useSession" \ components/frontend/src/app/ components/frontend/src/components/ --include="*.tsx"
Then check each file for `isLoading\|isPending` and `error` references.
Check `components/frontend/src/components/` for components imported only once. These should be co-located with their page in `_components/`.
New `page.tsx` files should reference `useWorkspaceFlag` or `useFlag` for feature gating.
# Frontend Review ## Summary [1-2 sentence overview] ## Findings ### Blocker [Must fix — or "None"] ### Critical [Should fix — or "None"] ### Major [Important — or "None"] ### Minor [Nice-to-have — or "None"] ## Score [X/8 checks passed]
Each finding includes: file:line, problem description, convention violated, suggested fix.
Kubernetes-native AI automation platform for intelligent agentic sessions
Review Go backend code for convention violations. Use after modifying files under components/backend/. Checks for panic usage,…
Runs all convention checks across the full codebase and produces a scored alignment report. Dispatched by the /align skill.
Review Kubernetes operator code for convention violations. Use after modifying files under components/operator/. Checks for…
Review Python runner code for convention violations. Use after modifying files under components/runners/ambient-runner/. Checks…
Cross-cutting security review for code touching auth, RBAC, tokens, or container specs. Use before committing any code that…