القائمة
Review accumulated retrospective findings in the learnings inbox and decide which to apply as guidelines, skills, architecture tests, or hooks. Use when the user wants to triage the inbox.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Create a git commit. Runs the test workflow as a pre-check, then formats the message per Conventional Commits with Argos-specific scopes.
Run a retrospective on recent work — typically on the develop branch, weekly. Analyzes recent commits, current diff, and conversation patterns to suggest improvements to guidelines, skills, architecture tests, or hooks. Triggers when the user says "retro", "let's review", or invokes /retro.
Run the full Argos quality suite — Pint (formatting), PHPStan/Larastan (static analysis), Pest (tests including architecture rules). Use before any commit, before opening a PR, or when the user asks to verify code quality.
استنادا إلى تصنيف SOC المهني
| name | review-learnings |
| description | Review accumulated retrospective findings in the learnings inbox and decide which to apply as guidelines, skills, architecture tests, or hooks. Use when the user wants to triage the inbox. |
| scope | argos |
cat .ai/learnings/inbox.md
If empty or missing, report: "No pending learnings to review."
The inbox is written in German — read and discuss accordingly. The user may converse in German or English at their preference.
For each finding, present it with three options:
For "Apply":
NEVER apply changes without per-finding confirmation. Do not batch-apply.
When all findings in the current inbox are processed, move the file to:
.ai/learnings/archive/YYYY-MM-DD-HHmm.md
(Use the date of the review, not the original finding dates.)
Creating a fresh empty inbox is not required — the next /retro will
create one if missing.
Report:
<path>