OpenParable
Skip to content
← Back to skills

Dagger Chores

Development
dagger-chores

Dagger Chores is an Agent Skill for development published in the dagger/dagger repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/dagger/dagger/blob/HEAD/skills/dagger-chores/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/dagger-chores, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Dagger Chores

Go Version Bump

Use this checklist when asked to bump Go.

  1. Update the Go version string in engine/distconsts/consts.go:
  • GolangVersion = "X.Y.Z"
  1. Update the Go default version string in toolchains/go/main.go:
  • // +default="X.Y.Z" on the version argument in New(...)
  1. Use a short commit message in this format:
  • chore: bump to go <major.minor>
  • Example: chore: bump to go 1.26
  1. Create a signed commit:
  • git commit -s -m "chore: bump to go <major.minor>"
  1. Tell the user to double-check whether new Go version locations have been introduced since the last bump, and mention they can ask the agent for help finding them.
  • Suggested wording: 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.

Regenerate Generated Files

Use this checklist when asked to regenerate generated files.

  1. From the Dagger repo root, create a temp file for command output and store its path in tmp_log.

  2. Run generation and redirect all output to the temp file:

  • dagger call generate layer export --path . >"$tmp_log" 2>&1
  1. Search the temp file as needed instead of printing full output.

  2. Delete the temp file when done.

Regenerate Golden Tests

Use this checklist when asked to regenerate telemetry golden tests.

  1. From the Dagger repo root, run dagger -c 'engine-dev | test-telemetry --update | export .'