branch

Documentation Branch

Scope: designed for strapi/documentation (and its forks).

Input

$ARGUMENTS: description of the work (e.g., "add MCP server page", "fix deployment steps for cloud").

If no arguments provided, ask what the branch is for.

Step 1: Detect prefix

Ask which area the work will touch, or infer from the description:

• Work only under docs/cms/ and/or static/ --> cms/
• Work only under docs/cloud/ and/or static/ --> cloud/
• Work touching both areas, or repo-level files --> repo/

If ambiguous, default to repo/ and mention it.

Step 2: Generate branch name

From the description, generate a slug: lowercase, hyphens, no special characters, concise.

Format: <prefix>/<slug> (e.g., cms/add-mcp-server-page, cloud/fix-deployment-steps).

Step 3: Create the branch

git checkout -b <branch-name>

Confirm with the branch name.