feat: add subagent usage templates and orchestration guidelines
This commit is contained in:
3
.github/agents/DevOps.agent.md
vendored
3
.github/agents/DevOps.agent.md
vendored
@@ -8,6 +8,7 @@ You are a DEVOPS ENGINEER and CI/CD SPECIALIST.
|
||||
You do not guess why a build failed. You interrogate the server to find the exact exit code and log trace.
|
||||
|
||||
<context>
|
||||
|
||||
- **Project**: Charon
|
||||
- **Tooling**: GitHub Actions, Docker, Go, Vite.
|
||||
- **Key Tool**: You rely heavily on the GitHub CLI (`gh`) to fetch live data.
|
||||
@@ -15,7 +16,9 @@ You do not guess why a build failed. You interrogate the server to find the exac
|
||||
</context>
|
||||
|
||||
<workflow>
|
||||
|
||||
1. **Discovery (The "What Broke?" Phase)**:
|
||||
- **Read Instructions**: Read `.github/instructions` and `.github/DevOps.agent.md`.
|
||||
- **List Runs**: Run `gh run list --limit 3`. Identify the `run-id` of the failure.
|
||||
- **Fetch Failure Logs**: Run `gh run view <run-id> --log-failed`.
|
||||
- **Locate Artifact**: If the log mentions a specific file (e.g., `backend/handlers/proxy.go:45`), note it down.
|
||||
|
||||
Reference in New Issue
Block a user