Skip to content
Skills Library
DevOps & cloud · Tool integration

setup

/setup

/factory:setup. Install Factory in the current repository on the user's consent: write .github/workflows/factory.yml from the Action's template, walk the Factory GitHub App creation, and apply the merge queue, branch protection, labels and Project board; or set up local mode on the user's own machine. Use when the user asks to set up, install or configure Factory for a repository.

Repository
factory ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

/factory:setup. Install Factory in the current repository on the user's consent: write .github/workflows/factory.yml from the Action's template, walk the Factory GitHub App creation, and apply the merge queue, branch protection, labels and Project board; or set up local mode on the user's own machine. Use when the user asks to set up, install or configure Factory for a repository.

Original author description

/factory:setup. Install Factory in the current repository on the user's consent: write .github/workflows/factory.yml from the Action's template, walk the Factory GitHub App creation, and apply the merge queue, branch protection, labels and Project board; or set up local mode on the user's own machine. Use when the user asks to set up, install or configure Factory for a repository.

How it works

  1. 1. The workflow file (--apply workflow)
  2. 2. The GitHub App
  3. 3. GitHub settings
  4. 4. Skills in the repository
  5. Local mode, instead of or beside the Action
  6. After
Original SKILL.md headings · 37 lines, 634 words
SKILL.md preview
---
name: setup
description: /factory:setup. Install Factory in the current repository on the user's consent: write .github/workflows/factory.yml from the Action's template, walk the Factory GitHub App creation, and apply the merge queue, branch protection, labels and Project board; or set up local mode on the user's own machine. Use when the user asks to set up, install or configure Factory for a repository.
---

# /factory:setup

Everything here changes the repository or its GitHub settings, so each step says what it will do and waits for a yes. The work is done by the plugin's `scripts/setup.mjs`: `node "${CLAUDE_PLUGIN_ROOT}/scripts/setup.mjs" --repo OWNER/NAME --apply <step> --yes`, one consented step at a time, where `<step>` is `workflow`, `labels`, `project` or `protection`. Without `--yes` the script only prints what it would do; use that as the preview before asking.

## 1. The workflow file (`--apply workflow`)

Ask once for the inputs the template needs and pass them as flags: `--harness` (claude, codex, copilot), `--model`, `--subagent-model`, `--reviewer-model`, `--max-concurrent`, `--daily-usd`, `--max-usd`, `--timeout-minutes` (under 360 on hosted runners), `--auto-merge` (default `true`: code then lands with no human read, gated by CI on the queue commit, the reviewer and the merge queue), `--credential` (`api`, or `plan` for the user's own repository only), `--notify`, `--runs-on` (default: the CI workflow's runner), `--setup`, `--validation`, `--budget-command`, `--protected-paths`, `--ci-checks`. Show the rendered `.github/workflows/factory.yml`; on yes, write it and say it needs a commit on the default branch to start its cron. A re-render keeps the file's settings: pass only changes (`--name=` clears one); show the kept and changed lines. It never triggers from a fork. `--sandbox vercel` writes the cloud-sandbox jobs instead (docs/ADAPTERS.md).

## 2. The GitHub App

Walk it; never read, print or copy the key.

1. Open `https://github.com/settings/apps/new` (or the organization's `/organizations/<org>/settings/apps/new`). Name it `Factory (<repo>)`, uncheck webhooks, and grant exactly these repository permissions: contents, pull requests, issues, projects: write; checks, commit statuses: read; actions: read, optional (cloud-sandbox logs and session restore); nothing else, never workflows.
2. Create it, generate a private key, note its App ID.
3. Install it on this repository only.
4. Save the two secrets: `gh secret set FACTORY_APP_ID` and `gh secret set FACTORY_APP_PRIVATE_KEY < path.pem`, run by the user, with the path they give as text.

Then the model credential, by the user (`gh secret set`): `ANTHROPIC_API_KEY` (none for Claude federation), `FACTORY_CODEX_GATEWAY_KEY` (an AI Gateway key) or `CODEX_API_KEY`, or `COPILOT_GITHUB_TOKEN` (only the Copilot Requests permission; doctor fails without it).

## 3. GitHub settings

- **Labels** (`--apply labels`) and **Project board** (`--apply project`, Projects v2 by GraphQL): as the App when the user exported `FACTORY_APP_TOKEN`, or `FACTORY_APP_ID` and `FACTORY_APP_PRIVATE_KEY="$(cat <path>.pem)"`, else as their `gh` login; never read the key.
- **Merge queue and branch protection** (`--apply protection`): the `factory` ruleset on the default branch (merge queue, required checks from `--ci-checks`, no deletion or force push) and squash commits from the PR's title and body. Rulesets need admin, which the App does not have, so this step runs as the user's own `gh` login. If the CI workflow lacks `merge_group:` under `on:`, offer to add the line.

## 4. Skills in the repository

Offer to commit the Factory skills and agent definitions (the vendors' cloud sessions need them): copy this plugin's `skills/*` to `.agents/skills/` and `.claude/skills/`, and `agents/<harness>/*` to `.claude/agents/`, `.codex/agents/` or `.github/agents/`, then commit. Say a committed Factory skill then overrides the plugin's, pinned at that version until updated.

## Local mode, instead of or beside the Action

For Factory on the user's own machine, walk `docs/LOCAL.md` instead of steps 1 to 3: no App, no model secret, and WSL2 only on Windows. The user creates a fine-grained token for this one repository (Contents, Issues and Pull requests read and write; Actions read), and for Copilot a Copilot Requests token. They save the tokens themselves with the command in that page; never ask for or read a token. Then offer `node "${CLAUDE_PLUGIN_ROOT}/scripts/local.mjs" serve --once` from the clone, which lists anything missing and creates the `factory:local` label. An Objective with that label is the local loop's, and the Action leaves it alone.

## After

Run `/factory:doctor` and show its lines. End with the one thing left for the user: commit the workflow, then label an issue `factory:objective`.

Versions

RepositoryScoreLicence
This page · clockgrove/factory90MIT
HwangSlater/harness-fit100MIT
nesquikm/dev-process-toolkit100MIT
userKael/rastro100MIT
als-apg/osprey100BSD-3-Clause
dedujeong/gemba100Apache-2.0
eigenwise/eigenwise-toolshed100MIT
awrshift/agent-memory-kit100MIT
lifecycle-innovations-limited/claude-ops100MIT

Database snapshot: 13.11.2026 · package version bffa2d537194 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 82factory-setup
    Set the Software Factory up in a new repository: check the machine, write the project file, prove the Gates on the base branch, create the labels and offer a trial Run. Use when the owner wants to start using the factory in a repository, or `factory doctor` fails.
  • 100queue
    /factory:queue. Start the unattended Factory scheduler for the current repository: dispatch the Action's workflow when .github/workflows/factory.yml exists, otherwise explain the harness-cloud scheduled-task path for this harness. Use when the user asks to queue, start, kick or…
  • 100factory-ci
    CI and pull-request review conventions. One canonical `.github/workflows/ci.yml` is the merge gate (typecheck, lint, test, build, claude-review); branch protection's required-checks list matches the job list 1:1; `anthropics/claude-code-action@v1` reviews every PR against the…
  • 100doctor
    /factory:doctor. Check that this repository, its GitHub settings, its model credential and its runner are ready for unattended Factory runs, and name the fix for each failure. Use when the user asks whether Factory is set up, why Objectives Block at the first step, or before enabling the workflow.
  • 100git-workflow-setup
    This skill configures Git Flow or GitHub Flow with branch protection and security settings. Use when the user asks "set up git flow", "configure branch protection", "set up git workflow", "protect branches", "Gitフロー設定", "ブランチ保護設定", or "ワークフロー設定".
  • 100graphite-setup
    Configure a GitHub repository for Graphite — branch protection, merge queue, CI triggers, and stack-aware CI optimizations. Use when the user is onboarding a repo to Graphite, mentions Graphite branch protection / required checks / signed commits / merge queue, sees CI failing…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.