Conversation
There was a problem hiding this comment.
Pull request overview
Adds a new “risk analysis” custom agent intended to assess PR/branch changes for security, safety, and operational risk, generate a Markdown report, and (when a PR exists) manage risk/* labels.
Changes:
- Introduces a new agent definition for PR risk & safety analysis.
- Specifies report output to
/reports/review-{branchname}.mdand risk label management behavior.
| # Pull Request Risk & Safety Analysis Agent | ||
|
|
||
| ## Trigger | ||
| Run when the agent is invoked in chat or via a command. If no PR exists, scan the current branch changes against the default branch. | ||
|
|
There was a problem hiding this comment.
This file is being added as a new custom agent, but it does not follow the repository’s established agent file conventions: agent files are *.agent.md and include YAML front matter (see docs/README.agents.md:8 and e.g. agents/address-comments.agent.md:1-8). As-is, this likely won’t be discoverable/usable as an agent. Rename to agents/analyst-risk-file-generator.agent.md and add front matter with at least a non-empty description (and typically tools, plus optional name/model).
| ## Objective | ||
| Analyze the pull request or current branch changes for security, safety, and operational risks. | ||
| Write a report file to `/reports/review-{branchname}.md` with the results. | ||
| If a PR is open, add a label `risk/{risk-level}` based on the detected risk level (low, medium, or high). | ||
| Do not create or update a PR. |
There was a problem hiding this comment.
New agent files should be added to the agents catalog (docs/README.agents.md) so users can discover/install them (the catalog is a table of agents; this new agent is not present). Please add an entry for this agent after renaming it to *.agent.md.
aaronpowell
left a comment
There was a problem hiding this comment.
Please review the contributing guide. Agent files need to have frontmatter to provide metadata for the agent, and the update script needs to be run.
Pull Request Checklist
npm startand verified thatREADME.mdis up to date.Description
Analyze the pull request or current branch changes for security, safety, and operational risks.
Write a report file to
/reports/review-{branchname}.mdwith the results.If a PR is open, add a label
risk/{risk-level}based on the detected risk level (low, medium, or high).Do not create or update a PR.
Type of Contribution
Additional Notes
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.