38 lines
1.4 KiB
Markdown
38 lines
1.4 KiB
Markdown
# 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`](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`](tasks/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:
|
|
|
|
```text
|
|
/mnt/assets/agent-tasks/<task-name>.task.md
|
|
```
|
|
|
|
The files are then available at:
|
|
|
|
```text
|
|
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.
|