
fallow-codex-onboarding
Set up the Fallow app in Codex after the plugin is installed: check the fallow installation, choose the default analysis scope, run the first analysis, and show the user where the dashboard, the Code Health tab, @Fallow mentions and the config editor are. Use when the user chooses Set up for Fallow in Codex, or asks to onboard or configure the Fallow app. Do not use for setting up lint, format or CI tooling; use fallow-setup for that.
- Installs
- 68
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/fallow-rs/fallow-skills --skill fallow-codex-onboarding- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads fallow-codex-onboarding automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Set up Fallow in Codex
Use the Fallow app tools. Keep each step short. Ask one question at a time.
1. Check the installation
Call fallow_check_install with {}.
- If it reports a version, continue.
- If fallow is missing, explain that the app runs the fallow CLI locally and
that no code leaves the machine. Offer to install it globally with
npm install --global fallow. The sidebar dashboard needs a fallow on PATH, because the app runs a copy inside the project only within the Codex sandbox of a thread. Run the install only after the user agrees. Then callfallow_check_installagain.
2. Choose the defaults
Call fallow_settings_read with {}. Ask these questions, one at a time.
Skip a question when the user already answered it.
- "Analyze the whole project by default, or only the files your branch
changed?" Map the whole project to
scope: "full"and changed files toscope: "changed". - "Leave tests, stories and dev tooling out of the analysis?" Map yes to
production: true.
Call fallow_settings_update with a set object that holds only the changed
values, for example {"set":{"scope":"changed"}}. Skip the call when nothing
changed. Report the saved values from the tool result. Do not say that a value
was saved when the call failed.
3. Run the first analysis
Call fallow_analyze with {}. The user sees the dashboard. In two or three
sentences, give the health score, the largest category of findings, and one
finding to start with.
If the result says that no project is known, ask the user to open a project
folder in this thread, then call fallow_analyze again.
4. Show what the app adds
Tell the user, in a short list:
- Fallow in the sidebar opens the full dashboard.
- Code Health opens beside a thread and follows the project of that thread.
- Type @Fallow in the composer to attach a finding or all findings of a rule.
- Open
.fallowrc.jsonor.fallowrc.jsoncto edit rules and preview their impact before saving..sariffiles open in a findings viewer. - Before a commit, ask Codex to audit the branch.
5. Offer the next step
If the project has no fallow config file (.fallowrc.json, .fallowrc.jsonc,
fallow.toml or .fallow.toml), offer the fallow-setup skill to add one and
a CI gate. If the user installed the plugin during another task, continue that
task in this conversation.
FAQ
What does the fallow-codex-onboarding skill do?
Set up the Fallow app in Codex after the plugin is installed: check the fallow installation, choose the default analysis scope, run the first analysis, and show the user where the dashboard, the Code Health tab, @Fallow mentions and the config editor are. Use when the user chooses Set up for Fallow in Codex, or asks to onboard or configure the Fallow app. Do not use for setting up lint, format or CI tooling; use fallow-setup for that.
How do I install fallow-codex-onboarding?
Run npx skills add https://github.com/fallow-rs/fallow-skills --skill fallow-codex-onboarding in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/fallow-codex-onboarding/ (personal) or .claude/skills/fallow-codex-onboarding/ (project).
Which AI agents can use fallow-codex-onboarding?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is fallow-codex-onboarding safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains fallow-codex-onboarding?
It is published by fallow-rs in fallow-rs/fallow-skills. It has 68 recorded installs.
More from fallow-rs/fallow-skills
fallow
fallow-rs/fallow-skills
Codebase intelligence for TypeScript and JavaScript. Static analysis reports changed-code risk, cleanup opportunities, duplication, circular dependencies, complexity hotspots, architecture boundaries, design-system drift, feature flags, and opt-in security candidates. Optional local similar-code discovery finds functions that may implement the same intent despite different syntax. Runtime coverage can merge production execution data. Use when asked to audit PR risk, find unused code or dependencies, compare semantically similar functions, detect duplicates, inspect architecture boundaries, merge runtime coverage, auto-fix supported issues, or run fallow.
fallow-review
fallow-rs/fallow-skills
Review AI-generated or human-written code changes with fallow's graph-grounded review brief. Subtracts deterministic concerns (unused code, complexity, duplication, styling) from the loop, ranks what to look at by blast radius and risk, and surfaces the few consequential structural decisions (new public-API contracts, coupling/boundary crossings, new dependencies) as framed judgment questions anchored to verifiable signals. Drives a closed agent-contract loop: fetch the walkthrough guide, return a judgment, and have fallow post-validate it against the live graph (hallucinated or stale judgments are rejected). Use when asked to review a PR, review a branch, review a diff, do a code review, or check changed code before merge.
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.