Respect a user policy of working on the default branch (ce-commit, ce-debug, ce-worktree, ce-test-browser, ce-dogfood)
Los mantenedores suelen responder en 1 día
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 22/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- git, markdown, playwright
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 25.6k
- Forks
- 2.1k
- Merge medio
- 3 h 57 min
- PR fusionados (30 d)
- 170
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de EveryInc/compound-engineering-plugin
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
EveryInc/compound-engineering-plugin#2085 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
EveryInc/compound-engineering-plugin#795 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 80/100
EveryInc/compound-engineering-plugin#2084 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
EveryInc/compound-engineering-plugin#2083 ·
Los mantenedores suelen responder en 1 día
-
Host support: DeepSeek Harness (dsh)Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
EveryInc/compound-engineering-plugin#2072 ·
Los mantenedores suelen responder en 1 día
Todos los issues de EveryInc/compound-engineering-plugin
Issues similares
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
elastic/kibana#306401 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
agentes-chat/agentes-chat#927 ·
Los mantenedores suelen responder en 1 día
-
[Bug]: Webapp workspace fails to render in Safari — "Can't find variable: requestIdleCallback"Abiertocomp/desktop P2 type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
NousResearch/hermes-agent#157702 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
e2e-failure ready-to-code
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
redhat-developer/rhdh-plugin-export-overlays#4794 · 1 comentario ·
Los mantenedores suelen responder en 1 día