원클릭으로
dagger-chores
// Handle quick, repeatable Dagger repository maintenance chores. Use when the user asks for small operational changes and wants the same established edits and commit style applied quickly.
// Handle quick, repeatable Dagger repository maintenance chores. Use when the user asks for small operational changes and wants the same established edits and commit style applied quickly.
| name | dagger-chores |
| description | Handle quick, repeatable Dagger repository maintenance chores. Use when the user asks for small operational changes and wants the same established edits and commit style applied quickly. |
Use this checklist when asked to bump Go.
engine/distconsts/consts.go:GolangVersion = "X.Y.Z"toolchains/go/main.go:// +default="X.Y.Z" on the version argument in New(...)chore: bump to go <major.minor>chore: bump to go 1.26git commit -s -m "chore: bump to go <major.minor>"Please double-check if any additional Go version strings were added in new files; these locations can change over time. If helpful, I can also help search for those locations.Use this checklist when asked to regenerate generated files.
From the Dagger repo root, create a temp file for command output and store its path in tmp_log.
Run generation and redirect all output to the temp file:
dagger --progress=plain call generate layer export --path . >"$tmp_log" 2>&1Search the temp file as needed instead of printing full output.
Delete the temp file when done.
Use this checklist when asked to regenerate telemetry golden tests.
dagger -c 'engine-dev | test-telemetry --update | export .'Covers Dagger Engine caching internals including cache key derivation, invalidation, and the immutable DAG model. Use when debugging cache misses, unexpected invalidations, or implementing caching-related engine features.
How to test Dagger engine changes. Covers manual e2e testing via the playground (bootstrapping a dev engine from source, running commands inside it, capturing crash logs) and running the integration test suite. Use when modifying engine code (engine/server, core/, dagql/) and needing to verify changes work. Triggers on: testing engine changes, dev engine, playground, e2e test, engine crash, debug engine, manual testing, verify engine fix.
Edit dagger.gen.go output, Go templates (object.go.tmpl, defs.go.tmpl), invoke() dispatch, SDK interfaces (CodeGenerator, ClientGenerator), `dagger develop`, `dagger client install`. Keywords: codegen, SDK, bindings, templates, internal/dagger, dag.*, ModuleMainSrc
Write design proposals for Dagger features. Use when asked to draft, review, or iterate on Dagger design documents, RFCs, or proposals.