Menu
Initialize ai-shell for a new repo or workspace and choose the correct repo type and tool setup.
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
| name | ai-init |
| description | Initialize ai-shell for a new repo or workspace and choose the correct repo type and tool setup. |
| argument-hint | [--library | --service | --workspace] [--codex | --claude | --opencode | --all] |
Set up AI tooling for this repository: $ARGUMENTS
Use this when starting a new repo or when ai-shell has not been initialized yet.
The goal is to choose the right repo type, install only the relevant skills, and avoid context litter.
Choose one:
library - package/published artifact, usually main branchingservice - deployable app/API/web/IaC repo, usually dev -> mainworkspace - coordination repo for multiple child reposIf the user does not specify a kind, ask once and persist it via ai-shell.toml.
Choose one:
--claude--codex--opencode--allPrefer initializing only the tool(s) the user actually uses.
Examples:
ai-shell init --library
ai-shell init --service
ai-shell init --workspace
ai-shell claude --init --service
ai-shell codex --init --library
ai-shell opencode --init --workspace
If the repo already has ai-shell.toml, prefer --update over --init.
Confirm that:
ai-shell.toml has the expected [project] metadataai-workspace-* skills and use uv run ai-tools workspace ...uv run ai-tools repo ...uv run ai-tools standardize ...For library / service repos:
/ai-pick-issue/ai-prepare-branch/ai-submit-work/ai-monitor-pipeline/ai-standardize-repo for standards alignment (uv run ai-tools standardize ...)For workspace repos:
/ai-workspace-sync/ai-workspace-status/ai-workspace-pick/ai-workspace-branch/ai-workspace-test/ai-workspace-lint/ai-workspace-submit/ai-workspace-update--update or --reset.iac, explain the current equivalent (service).Monitor CI pipeline after push, diagnose failures, auto-fix and re-push. Use after submitting work, or asking 'check the build' or 'how's the pipeline'.
Stand up a new repository with standard quality gates, CI/CD pipeline, and configuration files.
Find, analyze, and recommend GitHub issues to work on. Use when looking for issues, or asking 'what should I work on next'.
Create a feature branch from the correct base (dev or main), sync release bumps, and set up remote tracking. Use when starting work on an issue or saying 'start working on'.
Promote staging (dev) to production (main) by creating an automerge PR. Use when dev/staging is ready for release, or saying 'release to production'.
Comprehensive repository health check with remote-first git hygiene, branch cleanup, and code quality analysis. Use for repo maintenance, or saying 'clean up the repo'.