Run any Skill in Manus with one click

repo-setup

Stars0

Forks0

UpdatedApril 2, 2026 at 00:31

Set up repository policy and local Codex configuration for trunk-based development. Use when the user wants GitHub branch-protection guidance, `.codex/config.toml` direction, or a repo-local operating model aligned with direct trunk commits.

Installation

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.

Run Skill in Manus

Source

jwilger

jwilger/codex-sdlc

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	repo-setup
description	Set up repository policy and local Codex configuration for trunk-based development. Use when the user wants GitHub branch-protection guidance, `.codex/config.toml` direction, or a repo-local operating model aligned with direct trunk commits.

Repo Setup

This skill sets the repository-level rules around Codex usage.

Defaults

Protect main or the chosen trunk branch.
Require linear history.
Disable force-push.
Avoid a required-PR workflow unless the user explicitly wants one.

GitHub guidance

Recommend:

branch protection on trunk
linear history required
force-push blocked
optional required status checks only for checks that are fast and reliable enough to stay on the main path

Local Codex guidance

Keep the repo trusted in .codex/config.toml when appropriate.
Prefer repo-local AGENTS.md and repo-local plugin usage over home-global instruction sprawl.
Keep custom agents optional and task-specific.

Deliverables

A short branch-protection checklist
Any needed repo-local Codex config notes
A clear statement of what is enforced by GitHub versus what is enforced by skills and hooks

More from this repository

same repository

architecture-decisions

jwilger/codex-sdlc

Use this skill for ADRs, architecture choices, technology selection, boundaries, and updates to `docs/ARCHITECTURE.md`. It keeps research ahead of prose and requires explicit approval before a decision is treated as merged.

2026-04-020

event-modeling

jwilger/codex-sdlc

Use this skill to discover workflows, map events, commands, read models, automations, and Given/When/Then scenarios before implementation. It keeps discovery separate from architecture and implementation decisions.

2026-04-020

codex-review

jwilger/codex-sdlc

Review local changes before a trunk commit or push. Use when the user asks for review, a final preflight pass, or a regression check focused on correctness, risks, and missing tests.

2026-04-020

tdd

jwilger/codex-sdlc

Use this skill whenever the user wants test-first implementation. It runs a Codex-native RED -> DOMAIN -> GREEN -> DOMAIN -> COMMIT loop, with optional subagent delegation when explicitly useful.

2026-04-020

bootstrap-codex-sdlc

jwilger/codex-sdlc

Bootstrap a repository for Codex-first, trunk-based development. Use when the user asks to set up AGENTS.md, Codex workflow guidance, or repo-local SDLC defaults without centering Claude-specific conventions.

2026-04-020

bounded-delegation

jwilger/codex-sdlc

Keep Codex delegation explicit, sparse, and well-scoped. Use when the user asks for subagents, parallel work, or a multi-agent approach, or when a sidecar task is clearly parallelizable without changing the main workflow default.

2026-04-020

name	repo-setup
description	Set up repository policy and local Codex configuration for trunk-based development. Use when the user wants GitHub branch-protection guidance, `.codex/config.toml` direction, or a repo-local operating model aligned with direct trunk commits.

Repo Setup

This skill sets the repository-level rules around Codex usage.

Defaults

Protect main or the chosen trunk branch.
Require linear history.
Disable force-push.
Avoid a required-PR workflow unless the user explicitly wants one.

GitHub guidance

Recommend:

branch protection on trunk
linear history required
force-push blocked
optional required status checks only for checks that are fast and reliable enough to stay on the main path

Local Codex guidance

Keep the repo trusted in .codex/config.toml when appropriate.
Prefer repo-local AGENTS.md and repo-local plugin usage over home-global instruction sprawl.
Keep custom agents optional and task-specific.

Deliverables

A short branch-protection checklist
Any needed repo-local Codex config notes
A clear statement of what is enforced by GitHub versus what is enforced by skills and hooks