52 lines
2.1 KiB
Markdown
52 lines
2.1 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.
|
|
|
|
[`Agent.md`](Agent.md) is a generic repository instruction template. Its main
|
|
workflow is to preserve existing work, make narrowly scoped changes, verify
|
|
them, and record completed units in small, independently reviewable commits.
|
|
Copy it into a repository and add that project's architecture, toolchain,
|
|
commands, and domain-specific constraints.
|
|
|
|
## 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
|
|
|
|
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:
|
|
|
|
```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
|
|
```
|
|
|
|
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.
|