Respect a user policy of working on the default branch (ce-commit, ce-debug, ce-worktree, ce-test-browser, ce-dogfood)

Aperta
#2,071 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@tmchow ci sta già lavorando.

Dal 17/11/2026.

  • #2081 di @tmchow — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
22/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
git, markdown, playwright

Direzione di ricerca

Start with the branch and push steps in ce-commit/SKILL.md (step 2), ce-debug/SKILL.md, and ce-worktree/SKILL.md, then the scope logic in ce-test-browser/SKILL.md and ce-dogfood/SKILL.md. ce-work/references/workspace-setup.md shows how a session authorization is already read. The maintainers must first choose between reading a policy from instruction files and adding ce-setup config keys. Done means all five points follow that choice, with tests or docs covering each.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Some users work directly on a local default branch by policy. For example, a solo developer commits each unit of work on local main and has no PR flow. Three skills in 3.38.1 move work off the default branch without asking, two browser skills test nothing on the default branch, and nothing in the skills lets a user's standing instruction override that.

  1. ce-commit/SKILL.md, step 2 "Branch first": "if detached HEAD, or on the default branch ... create a feature branch ... Do not ask". ce-debug/SKILL.md, "Branch": "If the current branch is the default branch, create a feature branch without asking". The model can start both skills on its own, so a commit made during ordinary work leaves the default branch. ce-work/references/workspace-setup.md already allows a commit on the default branch when "the user explicitly authorized that in this session". A standing instruction in CLAUDE.md or AGENTS.md is not covered.

  2. ce-debug ships automatically when the origin accepts PRs: "Do not ask whether to open a PR; permission is not the gate". For a user whose standing rule is "never push", this skill pushes in any repository that has a PR-capable remote.

  3. ce-worktree/SKILL.md creates new work with git worktree add -b <branch> .worktrees/<branch> origin/<from-branch>. It uses the local ref only when origin/<from-branch> is missing. A user who keeps unpushed commits on local main gets a worktree that is missing those commits.

  4. ce-test-browser/SKILL.md finds its scope with git diff --name-only main...HEAD when the argument is current or empty. ce-dogfood/SKILL.md says "Never dogfood the trunk on a branch-name or blank target". When the user commits directly on local main, main...HEAD is empty, so both skills test nothing unless the user passes a ref. lfg runs ce-test-browser with no argument.

  5. ce-test-browser/SKILL.md says "Never install or substitute standalone Playwright, Puppeteer, a separately configured browser extension or MCP". ce-dogfood/SKILL.md has the same rule. A user whose instruction files name a browser MCP for UI testing, for example a Playwright MCP installed as a plugin, gets the opposite rule from these skills, and the skills fall back to agent-browser.

Request: let a standing instruction decide these five points. One way is to read the policy from the project and user instruction files, as ce-work already does for a session authorization. Another way is a setting in the ce-setup config, for example branch_policy: current-branch, ship: local-only, and worktree_base: local. With such a setting, ce-commit and ce-debug would commit on the current branch, ce-debug would stop before it pushes, and ce-worktree would branch from the local ref. For the browser skills, a commit range for the scope on the default branch (for example the commits since the last test run) and a browser_driver setting would cover points 4 and 5.

Lingua principale
TypeScript
Stelle
25.6k
Fork
2.1k
Merge medio
3h 57m
PR unite (30g)
170

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di EveryInc/compound-engineering-plugin

Tutte le issue di EveryInc/compound-engineering-plugin

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.