Repository adding agent tasks/prompts that I'm not keen on repeating over and over again
Go to file
Dandaedre e9f1e0e97e
Make task publication opt in
2026-10-03 00:42:47 +02:00
tasks Add reusable CI task briefs 2026-10-03 00:39:57 +02:00
.gitignore Initial commit 2026-10-03 00:28:07 +02:00
Jenkinsfile Make task publication opt in 2026-10-03 00:42:47 +02:00
LICENSE Initial commit 2026-10-03 00:28:07 +02:00
README.md Make task publication opt in 2026-10-03 00:42:47 +02:00

README.md

agent-tasks

Reusable task briefs for coding agents. Each brief captures a repeatable change, its constraints, and the checks needed before handoff, so project-specific work does not have to start from an improvised prompt.

Available tasks

  • ci-coverage-badges.task.md adds project-native coverage and publishes current version, test, and coverage badges without assuming a particular repository or build tool.
  • semi-harden-ci.task.md adds the focused cargo audit and cargo deny gates to any Cargo-based Rust project.

Copy the relevant brief into an agent session or reference it from a project task. The receiving agent must still read that project's own instructions and adapt the brief to its existing CI, tools, metadata, and commit conventions.

Publishing

Tasks are private to the repository by default:

  • tasks/ contains ordinary task briefs and is never published.
  • shared-tasks/ is an explicit opt-in publication directory.

The current briefs are in tasks/, so Jenkins has nothing to publish. To share a task publicly, move it to shared-tasks/. Jenkins validates that this optional directory contains only nonempty, regular *.task.md files. On main, it copies each shared file atomically to:

/mnt/assets/agent-tasks/<task-name>.task.md

The files are then available at:

https://assets.dandaedre.com/agent-tasks/<task-name>.task.md

If shared-tasks/ is absent or contains no task files, the pipeline succeeds without touching the asset mount. Other branches validate shared files but do not publish them. Publication intentionally does not delete files from the shared asset mount, so unsharing, removing, or renaming a task requires a separate, explicitly approved cleanup of its old public file.