Repository adding agent tasks/prompts that I'm not keen on repeating over and over again
Go to file
Dandaedre 32173a8fb8
Add reusable CI task briefs
2026-10-03 00:39:57 +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 Add reusable CI task briefs 2026-10-03 00:39:57 +02:00
LICENSE Initial commit 2026-10-03 00:28:07 +02:00
README.md Add reusable CI task briefs 2026-10-03 00:39:57 +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

The tasks/ directory is also the publication contract. Jenkins validates that it contains only nonempty, regular *.task.md files. On main, it copies each 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

Other branches are validated but are not published. Publication intentionally does not delete files from the shared asset mount, so removing or renaming a task requires a separate, explicitly approved cleanup of its old public file.