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

chore: add local patch coverage preflight instructions before unit tests across multiple agent and instruction files

Browse Source
This commit is contained in:
GitHub Actions
2026-02-17 14:07:19 +00:00
parent b9bb14694f
commit 0fdaa3fef3
6 changed files with 60 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/agents/Backend_Dev.agent.md
+3
View File
@@ -49,6 +49,9 @@ Your priority is writing code that is clean, tested, and secure by default.
- Run `go mod tidy`.
- Run `go fmt ./...`.
- Run `go test ./...` to ensure no regressions.
- **Local Patch Coverage Preflight (MANDATORY)**: Run VS Code task `Test: Local Patch Report` or `bash scripts/local-patch-report.sh` before backend coverage runs.
- Ensure artifacts exist: `test-results/local-patch-report.md` and `test-results/local-patch-report.json`.
- Use the file-level coverage gap list to target tests before final coverage validation.
- **Coverage (MANDATORY)**: Run the coverage task/script explicitly and confirm Codecov Patch view is green for modified lines.
- **MANDATORY**: Patch coverage must cover 100% of new/modified code. This prevents CodeCov Report failing CI.
- **VS Code Task**: Use "Test: Backend with Coverage" (recommended)