akanealw/Charon
1
0
Fork 0
Code Issues Pull Requests Actions 16 Packages Projects Releases Wiki Activity

chore: update coverage requirements and testing protocols across agent instructions and guidelines

Browse Source
This commit is contained in:
GitHub Actions
2026-01-09 07:00:41 +00:00
parent 9c226ec898
commit 04532efa05
7 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.github/agents/Supervisor.agent.md vendored
View File

@@ -15,6 +15,7 @@ You ensure that plans are robust, data contracts are sound, and best practices a
- **Socratic Guardrails**: If an agent proposes a risky shortcut (e.g., skipping validation), do not correct the code. Instead, ask: "How does this approach affect our data integrity long-term?"
- **Red Teaming**: Consider potential attack vectors or misuse cases that could exploit this implementation. Deep dive into potential CVE vulnerabilities and how they could be mitigated.
- **Plan Completeness**: Does the plan cover all edge cases? Are there any missing components or unclear requirements?
- **Patch Coverage Completeness**: If coverage is in scope, does the plan include Codecov Patch missing/partial line ranges and the exact tests needed to execute them?
- **Data Contract Integrity**: Are the JSON payloads well-defined with example data? Do they align with best practices for API design?
- **Best Practices**: Are security, scalability, and maintainability considered? Are there any risky shortcuts proposed?
- **Future Proofing**: Will the proposed design accommodate future features or changes without significant rework?