setup
/setup
Zapisuje konfigurację workflow funkcji w projekcie: workflow.json, reguły uprawnień, wpisy .gitignore i sprawdzenie wymagań.
- Autor
- trihuynh-agilityio ↗
- Repozytorium
- workez ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 11.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 11.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Zapisuje konfigurację workflow funkcji w projekcie: workflow.json, reguły uprawnień, wpisy .gitignore i sprawdzenie wymagań.
Oryginalny opis (EN)
Use when asked to set up, install, configure or re-check the feature workflow in a project. Writes the project's .claude/workflow.json, the permission rules in .claude/settings.json and the .gitignore lines the workflow needs, and checks the requirements. Re-run it after changing workflow.json.
Jak działa
- 1. Requirements
- 2. workflow.json
- 3. Settings and .gitignore
- 4. Optional: PR review in CI
- 5. Check and report
Podgląd SKILL.md
---
name: setup
description: Use when asked to set up, install, configure or re-check the feature workflow in a project. Writes the project's .claude/workflow.json, the permission rules in .claude/settings.json and the .gitignore lines the workflow needs, and checks the requirements. Re-run it after changing workflow.json.
allowed-tools: Read Write Edit Glob Grep AskUserQuestion Bash(*/scripts/doctor.sh*) Bash(git remote *) Bash(git branch*) Bash(git rev-parse *) Bash(git symbolic-ref *) Bash(git ls-remote *) Bash(gh auth status*) Bash(gh repo view *) Bash(command -v *) Bash(*/scripts/setup-project.sh*) Bash(bash */tests/run-all.sh*)
---
# Set up the feature workflow in a project
The workflow (`${CLAUDE_PLUGIN_ROOT}/WORKFLOW.md`) reads everything that differs between projects from `<project>/.claude/workflow.json`. Without that file every hook of this plugin does nothing. This skill writes it and the per-project files around it. It never commits, pushes or touches GitHub.
The project folder is the folder Claude was started in, unless the user names another (it may be a folder inside the repository, as in a monorepo).
## 1. Requirements
Run `${CLAUDE_PLUGIN_ROOT}/scripts/doctor.sh` from the project folder. Before `workflow.json` exists it checks only the machine: `git` 2.42+, `jq`, `gh`, `curl`, `lsof`, Node 18+ with `npx`, Google Chrome. Report what is missing with how to install it, and stop if `git` or `jq` is missing. The project must be inside a git repository.
Then pick the tracker (see "Local tracker" in `${CLAUDE_PLUGIN_ROOT}/WORKFLOW.md`). Look at `command -v gh`, `gh auth status` and `git remote -v`:
- `gh` is installed and signed in, and a remote points at github.com: suggest `github` (issues, sub-issues, PRs, review feedback and CI on GitHub).
- Otherwise (no `gh`, not signed in, a GitLab or other remote, or no remote): suggest `local` (tracking in `.claude/workflow/`, merge requests opened by the user, merges read from git).
Ask with `AskUserQuestion`, the suggestion first, and say in one line what the other choice would need. With `github`, stop if `gh` is missing or not signed in.
## 2. workflow.json
If `<project>/.claude/workflow.json` exists, read it, say so, and ask the user whether to keep it as is (go to step 3) or revise it.
Otherwise draft it from `${CLAUDE_PLUGIN_ROOT}/templates/workflow.example.json` (a full, working example for a Vite + FastAPI project) and the key reference at the end of `${CLAUDE_PLUGIN_ROOT}/WORKFLOW.md`. Fill every value from the project, never from the example:
- `tracker`: the choice of step 1.
- GitHub tracker: `github.repo`: `gh repo view --json nameWithOwner`. `github.remote`: the remote in `git remote -v` that points at it. `github.feedback_authors`: the user's GitHub login plus any review bot. `github.review_trigger`: `"@claude review"` if they will use the review workflow of step 4, else `""`.
- Local tracker: no `github` block. `remote`: the remote to push task branches to (ask when there are several), or `""` when the repository has none. The `naming` branches carry no issue numbers: `integration_branch` `feat/{feature_slug}`, `task_branch` `{task_type}/{feature_slug}-{task_slug}`, `task_pr_title` `{task_type}{task_scope}: {task_title}` (with `branches.prefix` instead of conventions, start them with that prefix).
- `branches.base`: the branch features start from and the final PR targets. Default `dev`: check it exists (`git ls-remote --heads <remote> dev`, or `git branch --list dev` without a remote). If it does not, say so and offer the repository's default branch (`git symbolic-ref refs/remotes/<remote>/HEAD`, else `main` or `master`, whichever exists). Ask with `AskUserQuestion`, `dev` first when it exists; the user may type any other branch name, and that name is used everywhere (`branches.base`, `branches.protected`, the CI template of step 4). `branches.protected`: the base and the release branches (by default the base plus `main` when it exists).
- `conventions`: keep the example's [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) setup (`commit_types` and `subject_max_length` 72) unless the project already follows another commit convention; ask before dropping it. With it, branches are `<type>/<issue>-<slug>` and the `naming` patterns use `{task_type}` and `{task_scope}` as in the example. Without it, set `branches.prefix` (for example `feat/`), which every `naming` branch must start with.
- `docs_dir`: where feature docs go, for example `docs/features`.
- `commands`: read `package.json` scripts, `pyproject.toml`, `Makefile`, `CLAUDE.md` and CI files for install, build, lint, format check and test, each `{dir, run}` relative to the project. `commands.acceptance` runs given test files and writes a report file (`{output}`, `{files}`), in any format its test runner offers (JSON, JUnit XML).
- `format`: one rule per formatter actually configured in the project.
- `lanes` (exactly `A` and `B`), `dev_servers`, `app_url`, `dev_url`: how to start the app on two separate sets of ports, each with a `ready` URL. Ask if the project has no UI; the UI checks are then skipped by the plan.
- `blocked_commands`: the project's own "never run" rules from `CLAUDE.md` (wrong package manager, deleting the database, ...).
Show the draft and ask the user to approve it (`AskUserQuestion`) before writing it.
## 3. Settings and .gitignore
Run `${CLAUDE_PLUGIN_ROOT}/scripts/setup-project.sh --dry-run` from the project folder and show the user the result: the permission rules it merges into `.claude/settings.json` (gh rules for the repo with the GitHub tracker only, git fetch and push rules for the remote and branch prefixes when there is a remote, the project's commands, the plugin scripts, the two Playwright servers; deny rules for merges, force pushes, protected branches and approvals) and the lines it adds to `.gitignore`. After the user agrees, run it without `--dry-run`. It keeps every existing setting and adds each rule once.
## 4. Optional: PR review in CI
GitHub tracker only; skip this step with the local tracker. The build expects a reviewer on each task PR. Offer to copy `${CLAUDE_PLUGIN_ROOT}/templates/github-workflows/claude-review.yml` to `.github/workflows/` at the repository root, with `@claude review` replaced by `github.review_trigger` (keep `feat/`: it matches the integration branches, which are the task PRs' base; with `branches.prefix` instead of conventions, use that prefix). It needs the `CLAUDE_CODE_OAUTH_TOKEN` secret, which only the user can add.
## 5. Check and report
Run `${CLAUDE_PLUGIN_ROOT}/scripts/doctor.sh` again and fix what it reports as `FAIL` that this skill owns (`workflow.json`, permissions, `.gitignore`); list the rest for the user. Then tell the user:
- what was written, and that `.claude/workflow.json` and `.claude/settings.json` should be committed;
- that each person can turn the macOS notifications off for themselves with `{ "notify": false }` in `.claude/workflow.local.json` (gitignored, never committed);
- that `CLAUDE.md` should describe the stack, rules and how to run one test, since every phase reads it;
- to run `/reload-plugins` (or start a new session) so the hooks see the new config;
- how to start: `/workez:plan-feature <idea>`;
- with the local tracker: that they open each merge request themselves from the file the workflow writes, and say "T3 is merged" in chat after a squash merge.
Install the plugin per project (`claude plugin install workez@workez --scope project`) when the user does not want its Playwright servers in every project.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · trihuynh-agilityio/workez | 100 | MIT |
| HwangSlater/harness-fit | 100 | MIT |
| nesquikm/dev-process-toolkit | 100 | MIT |
| userKael/rastro | 100 | MIT |
| als-apg/osprey | 100 | BSD-3-Clause |
| dedujeong/gemba | 100 | Apache-2.0 |
| eigenwise/eigenwise-toolshed | 100 | MIT |
| awrshift/agent-memory-kit | 100 | MIT |
| lifecycle-innovations-limited/claude-ops | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 67c9fea6ae4b (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100configure-gitignore
Zarządza blokiem Claude Code w .gitignore (worktrees, blokada zadań cyklicznych, lokalne ustawienia), przy wdrażaniu repozytorium lub braku wpisów Claude. - 100init-repo
Zakłada od zera repozytorium workflow n8n: struktura katalogów, CLAUDE.md, README, .gitignore, .env.example, konfiguracja n8nac, pobranie schematów węzłów i weryfikacja. - 100project-init
Prowadzi wywiad, jedno pytanie naraz, i generuje od zera CLAUDE.md, ROADMAP, .gitignore oraz .env.example dla nowego projektu. - 100setup-gitignore
Tworzy lub idempotentnie poprawia .gitignore, łącząc szablony gitignore.io, wzorce narzędzi AI i IDE oraz potwierdzone śmieci z git status. - 100gitignore-builder
Buduje i scala pliki .gitignore z szablonów github/gitignore z inteligentnym wykrywaniem projektu. - 100godot-project-setup
Zakłada nowy projekt Godot 4.x z zalecaną strukturą katalogów, ustawieniami projektu, autoloadami i plikiem .gitignore.