Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

repo-setup

Estrellas0

Forks0

Actualizado2 de abril de 2026 a las 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.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

jwilger

jwilger/codex-sdlc

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·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

Más de este repositorio

mismo repositorio

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