Respect a user policy of working on the default branch (ce-commit, ce-debug, ce-worktree, ce-test-browser, ce-dogfood)
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 22/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- git, markdown, playwright
- Domain
- developer-experience, testing-qa, tooling
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
-
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.mdalready 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. -
ce-debugships 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. -
ce-worktree/SKILL.mdcreates new work withgit worktree add -b <branch> .worktrees/<branch> origin/<from-branch>. It uses the local ref only whenorigin/<from-branch>is missing. A user who keeps unpushed commits on localmaingets a worktree that is missing those commits. -
ce-test-browser/SKILL.mdfinds its scope withgit diff --name-only main...HEADwhen the argument iscurrentor empty.ce-dogfood/SKILL.mdsays "Never dogfood the trunk on a branch-name or blank target". When the user commits directly on localmain,main...HEADis empty, so both skills test nothing unless the user passes a ref.lfgrunsce-test-browserwith no argument. -
ce-test-browser/SKILL.mdsays "Never install or substitute standalone Playwright, Puppeteer, a separately configured browser extension or MCP".ce-dogfood/SKILL.mdhas 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 toagent-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.
- Dominant language
- TypeScript
- Stars
- 25.6k
- Forks
- 2.1k
- Avg merge
- 3h 57m
- Merged PRs (30d)
- 170
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EveryInc/compound-engineering-plugin
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EveryInc/compound-engineering-plugin#2085 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
EveryInc/compound-engineering-plugin#795 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 80/100
EveryInc/compound-engineering-plugin#2084 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
EveryInc/compound-engineering-plugin#2083 ·
Maintainers usually reply within 1 day
-
Host support: DeepSeek Harness (dsh)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 48/100
EveryInc/compound-engineering-plugin#2072 ·
Maintainers usually reply within 1 day
All issues in EveryInc/compound-engineering-plugin
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
hurttlocker/o8#6535 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
area: backend bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
snapotter-hq/SnapOtter#4856 ·
Maintainers usually reply within 1 day
-
bug follow-up
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
spellshift/realm#2509 ·
Maintainers usually reply within 1 day