Przejdź do treści
Biblioteka skilli
Programowanie · Automatyzacja

arrange-cycle-commit

/arrange-cycle-commit

Dzieli gotową pracę na małe, opisane commity, scala gałęzie zgodnie z kontraktem i wypycha je, nigdy nie wypychając gałęzi main.

Repozytorium
regency ↗
Licencja
MIT
Ostatnia zmiana repozytorium
06.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 06.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Dzieli gotową pracę na małe, opisane commity, scala gałęzie zgodnie z kontraktem i wypycha je, nigdy nie wypychając gałęzi main.

Wyzwalacze z opisu

s own, else the Regentcommit and mergeprepare the mergesepare os commits

Argumenty

/arrange-cycle-commit [scope]
Oryginalny opis (EN)

Regency arrange-cycle-commit. Split the finished work into small, described commits (feat, fix, docs, add, test kept apart), merge up to main following the branch contract (the project's own, else the Regent's default plumbing → testing → main), then push every branch except main. Never pushes main: the Regent does, and a hook enforces it. Use for /regency:arrange-cycle-commit, or when the Regent says commite, mescle, 'commit and merge', 'prepare the merge', 'separe os commits'.

Jak działa

  1. 0. Preconditions
  2. 1. Split
  3. 2. Commit
  4. 3. Merge up to main
  5. 4. Push the branches — never main
  6. 5. Report
  7. Boundaries
Sekcje z nagłówków SKILL.md, w oryginale · 104 linii, 971 słów
Podgląd SKILL.md
---
name: arrange-cycle-commit
description: "Regency arrange-cycle-commit. Split the finished work into small, described commits (feat, fix, docs, add, test kept apart), merge up to main following the branch contract (the project's own, else the Regent's default plumbing → testing → main), then push every branch except main. Never pushes main: the Regent does, and a hook enforces it. Use for /regency:arrange-cycle-commit, or when the Regent says commite, mescle, 'commit and merge', 'prepare the merge', 'separe os commits'."
argument-hint: "[scope]"
disable-model-invocation: true
---

# arrange-cycle-commit — split, commit, merge up to main, push the branches (never main)

> **Root.** This file is `skills/arrange-cycle-commit/SKILL.md`; the regency root is two
> directories above it. Paths like `library/…` are relative to that root. Read
> `library/conventions.md` §4 (Git) and locate the project's documents with `library/layouts.md`.

## 0. Preconditions

Run `git status` and `git branch --show-current`. Stop and say so if this is not a git repository.

1. **Learn the branch contract** from the project's docs (the entry index, `AGENTS.md`, a "branch
   flow" section): which branch carries which kind of work, what merges onto what, what the
   verification command is, and any rule such as "code commits carry no new tests" or "tests are a
   separate pass". Quote the rule you are applying. When the project documents none, apply the
   Regent's default (`library/conventions.md` §4: `plumbing` → `testing` → `main`) and say so in the
   report. When a branch of the contract does not exist yet, **ask** (pop-up) before creating it;
   committing on the current branch needs no such answer.
2. **Whose changes are these?** List every modified/untracked file. Group them into: (a) work done in
   this session, (b) everything else. Stage only (a). Files in (b) belong to the Regent: leave them
   untouched and unstaged, and name them in the report. If a file mixes both, ask.
3. **The Regent authors, Claude co-authors** (`library/conventions.md` §4). The author is the identity git
   resolves here (`git var GIT_AUTHOR_IDENT`); set none of your own. If this repository's config overrides it with
   `noreply@anthropic.com`, remove the override (`git config --local --unset user.name`,
   `git config --local --unset user.email`) and say so in the report. If git then resolves no identity, or only
   Claude's, ask.

## 1. Split

Group (a) into the smallest coherent commits, one purpose each:

| Type | For |
|---|---|
| `feat` | a new capability the user can perceive |
| `fix` | a defect repaired (always its own commit) |
| `docs` | guideline, plan, changelog, README changes |
| `add` | a new file or resource with no behaviour yet |
| `test` | tests only — never inside a code commit unless the compiler forces the adaptation |
| `refactor` / `chore` | structure or tooling with no behaviour change |

Order them so each commit builds and passes on its own ("one step per commit, green at each step").
Format-only differences ride with the commit that touched the lines.

## 2. Commit

For every commit: stage exactly its files (`git add <paths>`, never `-A`/`.`), run the project's
verification command if it is quick and available, then commit with a message that states **what
changed and why**, in the project's language and commit style (read `git log` for it). Body in
detail for anything non-obvious. End the message with the attribution line the harness gives,
`Co-Authored-By: Claude <Model> <noreply@anthropic.com>`.

Never use `--no-verify`, never amend a commit that is not yours from this run, never rewrite
history, never create a worktree.

## 3. Merge up to main

**Drafts hold the merge.** Before any merge past `plumbing`, run `python scripts/vp.py drafts`. Exit 1
means a speed mode's DRAFT/UNVERIFIED work is still on `plumbing` (`library/team/SPEED_MODES.md` §6):
merge nothing past `plumbing`, list the drafts in the report, and name the `/regency:team` passes that
would verify them.

Follow the contract from §0, branch by branch, in the documented direction. Prefer the project's
stated method (fast-forward vs merge commit). After each merge run the verification command.
Conflicts: resolve only the ones inside your own commits' files; anything else → stop and ask.
Do not merge onto `main` unless the contract says that is the next step.

## 4. Push the branches — never `main`

After the commits and merges, push **the branches this run touched, except `main`/`master`**:

1. **Check the remote and the branch.** Use `origin` unless the project documents another remote. No
   remote → skip the push and say so. Skip a branch that is already level with its remote.
2. **Ask first when a push is more than a push.** If the project docs say that pushing a branch
   triggers a pipeline — a build, a migration, a deploy, anything on cloud or production — do not
   push it: put it in a pop-up (pushing it is a cloud-adjacent act, `library/conventions.md` §5–§6)
   and let the Regent decide. Read the branch flow documents for this; do not guess.
3. **Push plainly:** `git push -u origin <branch>`, one branch per command, so each can succeed or
   fail on its own. Never `--force`, `--force-with-lease`, `--all`, `--mirror`, `--delete`; never
   tags unless the order asks for them.
4. **A rejection stops that branch.** Non-fast-forward or any refusal: report it with the message and
   leave it for the Regent. Do not retry with force, and do not rebase to make it fit.
5. **`main` is never pushed by an agent.** A hook (`scripts/guard-push.py`) blocks it; do not look for a
   way around it, and do not push `main` under another name (`HEAD:main`, `refs/heads/main`). When
   `main` is ready, say so: the push is the Regent's act.

## 5. Report

```text
Commits   <n>   – <hash> <subject> (one line each)
Merged    <branch> → <branch> … (or "none: <why>")
Held      <n> unverified draft(s) on plumbing: <units> (or omit the line when vp.py drafts exits 0)
Verified  <command> → green | red <where>
Pushed    <branch> → origin (or "none: <why>"; branches held back for a pipeline: <list>)
Untouched your uncommitted files: <list> (not staged)
Ready     main is at <hash>; push is yours.
Assumed X because the order did not say Y. Next time: <rewritten order>.   ← only if you assumed
```

## Boundaries

No push of `main`/`master`, no force, no tags unasked, no history rewrite, no worktree, no staging of
others' changes, no cloud or production command (a push that starts a pipeline counts as one), no merge
outside the documented contract.

Wersje

W bazie nie ma innych skilli o nazwie arrange-cycle-commit.

Migawka bazy z 13.11.2026 · wersja paczki cd1034dc5b78 (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

  • 90commit-push-main
    Commituje i wypycha zmiany bezpośrednio do domyślnej gałęzi na wyraźną prośbę, bez gałęzi roboczej i pull requestu.
  • 100ship
    Wysyła gotową pracę standardową drogą: bramki lokalne, commit, push, PR i CI na zielono, nigdy bezpośrednio do main.
  • 90commit-push-current
    Commituje i wypycha zmiany do bieżącej gałęzi na prośbę człowieka, bez tworzenia gałęzi i pull requestu.
  • 100commit-push
    Zatwierdza zmiany i wypycha je na zdalną gałąź bieżącego repozytorium, z ochroną gałęzi main i master.
  • 95dev_gate_merge-to-main
    Egzekwuje workflow gałęzi funkcji: przechwytuje próby merge, push lub commitu wprost do main i kieruje na właściwy proces z gałęzią funkcji.
  • 100git-merge-into-main
    Scala gotową, zrecenzowaną i zacommitowaną gałąź do gałęzi domyślnej w repozytorium, które integruje się wprost do main, bez pull requesta.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.