Menu
Project-level overrides for the commit-commands commit-push-pr skill. Adds auto version-bump heuristic and bisectable commit guidance.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Drive the permanent fresh-install staging environment — a customer-identical `npx orionfold-relay` first-run against an isolated data dir. Use when the user mentions staging, fresh-install testing, customer-experience simulation, "spin up staging", "launch the staging instance", tear down staging, isolated data-dir launch, reproducing a customer report, or seeding/clearing staging scenarios. Also triggers on "relay-staging", "staging harness", "customer first-run", "PLG-S", "simulate a customer install", or any request to stand up a clean isolated Relay instance the operator can watch. This is the SUBSTRATE the staging-cli-run / staging-browser-smoke / staging-evaluate skills ride on; invoke it first to prepare a running instance. Do NOT use for dogfooding from a git worktree (use worktree-production) or for the ephemeral CI smoke.
Technical architecture advisor that maintains Technical Decision Records (TDRs) and advises on system design, integration patterns, architectural changes, and drift detection. Use this skill when the user asks about architecture review, system design, blast radius analysis, integration design, technical decisions, pattern consistency, coupling analysis, technical debt assessment, TDR management, architecture drift, or pattern drift. Also triggers on "architecture review", "blast radius", "impact analysis", "integration design", "TDR", "technical decision", "pattern audit", "coupling", "tech debt", "architecture health", "how should this integrate", "what's the architectural impact", "what breaks if I change", "document this decision", or any question about system-level design, cross-cutting concerns, architectural trade-offs, or whether the codebase is drifting from its own conventions. Do NOT use for building components, UX review, writing feature specs (use product-manager), running tests (use quality-manag
Scaffold an ainative-native app by composing existing primitives (agent profiles, workflow blueprints, user tables, schedules, document routing) from a YAML manifest instead of writing TypeScript. Use when the user asks to "create an ainative app", "scaffold an app", "build an app manifest", "design an app in ainative", "wealth-manager-style app", "app from config", "compose an ainative app", or when they want to package a workflow + profile + schedule + table combination as a reusable bundle. Also triggers when the user wants to turn an ad-hoc workflow into a shippable app or when a proposed feature can be built entirely by composition of existing primitives. Do NOT use for writing new TypeScript components, new DB migrations, new chat tools, or net-new primitive kinds — those are outside the config-over-code contract; route to `product-manager` or `architect` instead.
Transform raw product ideas into structured, implementable feature specs. Use this skill whenever the user mentions grooming features, creating a roadmap, extracting features from ideas, updating feature status, checking what to build next, prioritizing work, maintaining a changelog, or managing product backlog. Also triggers on "what should we build", "groom", "feature spec", "roadmap update", "mark feature as", "what's the status", "prioritize", or any request to turn ideas into actionable development tasks. If the user has an ideas/ directory and wants to organize it into buildable units, use this skill.
Meta-orchestrator that reads project state holistically to recommend what to work on next. Use this skill when the user asks "what should I work on next", "project health", "status overview", "plan a sprint", "are we on track", "vision check", "retro", "lessons learned", "what's the priority", or any question about overall project direction, velocity, or process improvement. Do NOT use for writing feature specs (use product-manager), building components directly, running tests (use quality-manager), or UX review.
Sensitive-material analyst intended only for an operator-verified, locally hosted Ollama endpoint with network tools disabled
| name | commit-push-pr-overrides |
| description | Project-level overrides for the commit-commands commit-push-pr skill. Adds auto version-bump heuristic and bisectable commit guidance. |
These overrides augment the base commit-commands:commit-push-pr skill. Apply these rules IN ADDITION to the plugin's base behavior.
If staging multiple files across different concerns, suggest grouping into logical commits that each pass tests independently. Each commit should be a coherent unit of change (e.g., separate "add schema migration" from "add UI component"). Ask the user before splitting if unsure.
Check if package.json exists and suggest a version bump:
Present the suggestion and wait for confirmation before bumping. Skip if user declines or if no package.json.
