Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →camunda/operate-engineering-loop
Drive a tracked Operate change in the orchestration cluster webapp (src/operate/) end to end — issue branch, implementation, gated validation, independent review, a draft PR, and repeated Copilot review resolution.
Passed 18 of 19 test cases with the skill, and 3 of 19 without it.
and 18 more in the full report
15 fixed3 passed either way1 still failing0 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which specific directory paths define the frontend code scope owned by the Operate engineering loop?
| Checked | Without skill | With skill |
|---|---|---|
| specifies webapp/client/apps/orchestration-cluster-webapp/src/operate/ as primary scope | Missed | Passed |
| specifies src/routes/ and src/shared/ as secondary scopes | Missed | Passed |
The instructions your model reads when the skill loads.
Own a tracked Operate change from issue to a review-ready draft PR. Return to the engineer only after the implementation, independent reviews, required PR checks, and Copilot review loop are complete.
Scope is the Operate pod at webapp/client/apps/orchestration-cluster-webapp/src/operate/, plus
the route files in src/routes/ and cross-pod primitives in src/shared/ that the change requires.
Read frontend-unit-test for browser-mode unit tests and
frontend-integration-test for Playwright tests. For the
app's directory layout, pod areas and shared-code boundaries, see
docs/monorepo-docs/frontend/orchestration-cluster-webapp.md. Operate's own conventions — routing,
data fetching, state, styling, testing — are in
operate-frontend.
An explicit engineering-loop invocation, directly or through frontend-operate-migrator, authorizes local edits, branch creation, commits, pushes, draft PR creation, independent agent reviews, Copilot review requests, and handling review threads. This applies to execution, not analysis or planning. It does not authorize marking the PR ready, merging it, or changing unrelated code. Later user instructions replace the relevant permission; never carry permissions over from another invocation.
Human/team PR reviewer and assignee selection belongs to the user. Do not request or assign them unless the user explicitly names them.
This skill stops at a review-ready draft PR by default. When updating an existing PR, preserve its current state unless the user instructs otherwise. Send progress only at the end.
Required:
camunda/camunda issue number or URL.Optional:
test cases passed, vs 3 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.