Templates & agent setup prompts¶
Start with the workflow you need. Each template is a small, editable starting point—not a new service to operate. Give its setup prompt to your coding agent inside the target repository.
| Template | Trigger | Result | Start here |
|---|---|---|---|
| Prism-style SDK upkeep | Scheduled CI or manual run | Compatibility patch / reviewed PR | Setup prompt · YAML |
| Script-driven maintenance | Python or Node script | Checked patch and structured result | Setup prompt · Python · JavaScript |
| Vulnerability reporting | Authenticated scanner webhook | Findings list in Slack | Setup prompt · Report payload |
| Vulnerability remediation | One authenticated finding | Tested GitHub PR + Slack outcome | Setup prompt · Fix payload · Workflow |
For first-time setup, use the focused agent prompt library: local setup, GitHub Actions, SDK scripts and run diagnosis. Each prompt specifies what the agent should inspect, produce and verify, and where setup stops.
A setup prompt you can use now¶
Copy this into your coding agent, changing the selected template:
Set up Repo Maintainer in this repository using the Prism, script, or security
template from https://github.com/djsydney04/repo_maintainer/tree/main/templates.
Read that template's SETUP.md and inspect this repository before editing.
Use its actual language, package manager, source paths, tests and build.
Choose one focused task. Keep permitted edits narrow and checks meaningful.
Add relevant official web sources as evidence. Use YAML for a recurring job
or an SDK configuration object for a script; do not require both.
Keep credentials out of files and logs. Validate configuration without model
calls, run relevant tests, and show the resulting diff. Explain the trigger,
result, required secrets, and anything not yet verified. Do not merge fixes,
publish releases, or send test reports to a live Slack channel during setup.
The individual prompts add the details for each workflow. They ask the agent to adapt the template rather than copy assumed paths or tests.
What is included¶
The security bundle contains a trusted Python configuration, a worker, a GitHub Actions workflow and example dispatch payloads. Report jobs post to a configured Slack incoming webhook. Fix jobs call the Python SDK, retain a checked patch, and use a separate publishing job to open a PR. Notifications link to the Actions run with its PR URL and evidence.
The scanner-specific public webhook receiver is not included. Your gateway verifies signatures, authorizes the destination and deduplicates deliveries, then sends an authenticated GitHub dispatch. It must keep a durable queue if every event must be processed; GitHub concurrency alone is not such a queue. Follow the setup prompt for that integration.
These files are templates, not active installations. No Slack channel, scanner, or target repository is connected just by installing the SDK.
Choose where configuration lives¶
- YAML: readable project policy checked into a repository.
- Python dictionary / TypeScript object: a script chooses and supplies the complete configuration. The engine applies exactly the same schema and checks.
- JSON request from another script: pipe an object containing config and optional task into the CLI's request input.
See CLI requests, Python, TypeScript, or Rust. Configuration can include web-page context through any of these interfaces.