Skip to content

Commit d90b077

Browse files
committed
Auto-commit from sys76
AGENTS.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)
1 parent adb9961 commit d90b077

1 file changed

Lines changed: 16 additions & 0 deletions

File tree

AGENTS.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -99,3 +99,19 @@ def test_slot_emits_signal(qtbot, mocker):
9999
- **Docstrings**: Google-style on all public APIs
100100
- **Signals for cross-layer communication**: never call View methods from ViewModel
101101
- **Long operations**: must use `QThread`, never block the UI thread
102+
103+
## Codex Code Review
104+
105+
- For comprehensive repo reviews, save reports to `docs/code-reviews/` as new timestamped Markdown files.
106+
- Review implementation code by default, not the test suite as a standalone review target, unless I explicitly ask for a test review.
107+
- If I explicitly ask for a test review, use the dedicated test-suite review workflow and save reports to `docs/test-reviews/` as new timestamped Markdown files.
108+
- If I explicitly ask for a security review, use the dedicated security-review workflow and save reports to `docs/security-reviews/` as new timestamped Markdown files.
109+
- If I explicitly ask for an API contract review, use the dedicated api-contract-review workflow and save reports to `docs/api-contract-reviews/` as new timestamped Markdown files.
110+
- If I explicitly ask for an observability review, use the dedicated observability-review workflow and save reports to `docs/observability-reviews/` as new timestamped Markdown files.
111+
- If I explicitly ask for a CI review or CI/CD review, use the dedicated ci-cd-review workflow and save reports to `docs/ci-reviews/` as new timestamped Markdown files.
112+
- If I explicitly ask for a UI review, UX review, or accessibility review, use the dedicated ui-ux-accessibility-review workflow and save reports to `docs/ui-reviews/` as new timestamped Markdown files.
113+
- If I explicitly ask for a performance review, use the dedicated performance-review workflow and save reports to `docs/performance-reviews/` as new timestamped Markdown files.
114+
- Read `docs/conventions.md` when present and treat it as a primary review input.
115+
- If no conventions file exists, recommend creating `docs/conventions.md` and propose concrete project-specific conventions based on the codebase.
116+
- Write the saved report for Claude Code as the primary reader.
117+
- At the top of the report, suggest Claude use the `superpowers:receiving-code-review` skill.

0 commit comments

Comments
 (0)