Menü
Read a review report and apply fixes to the codebase
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Review an Equal Experts Gen AI Engineer take-home test submission (typically a RAG pipeline exercise) against the EE assessment rubric. Use when reviewing a candidate's Gen AI / LLM / RAG take-home test, assessing a retrieval-augmented-generation or prompt-engineering exercise, or scoring a THT for a Gen AI Engineer role.
Review an Equal Experts Backend Software Engineer take-home test submission against the EE assessment rubric. Use when reviewing a candidate's backend / general software engineering take-home test (non Gen AI), assessing a coding exercise submission, or scoring a THT for a backend role.
Generate a single-line commit message from conversation context and git diff, then optionally commit
Shared code and test patterns for the story pipeline skills
Write tests and implementation together for a user story
Final quality review producing a human-readable report
Basierend auf der SOC-Berufsklassifikation
| name | fix |
| description | Read a review report and apply fixes to the codebase |
Read a code review report and apply all necessary fixes. Critical findings are mandatory. Warnings are applied unless disproportionate. Suggestions are skipped.
$ARGUMENTS is the path to a story file.
Derive story-slug from the story filename. Read docs/reviews/{story-slug}/02-review.md.
If the report status is PASS, there is nothing to fix. Write a brief summary to docs/reviews/{story-slug}/03-fix.md noting no fixes were needed, and stop.
Discover the project's test and lint commands by exploring project configuration files. Look at existing source files to understand the code style.
Categorise the findings:
For each Critical finding, then each Warning:
Do not introduce new features or refactor beyond what the findings require.
Run the project's test command. All tests must still pass after fixes.
If a fix breaks a test, the fix is wrong — revert it and try a different approach. Tests are the source of truth.
Run the project's lint and type-check commands. Fix any issues introduced by the fixes.
Write to docs/reviews/{story-slug}/03-fix.md:
# Phase 3: Fixes Applied
**Story:** {story file path}
**Date:** {ISO date}
## Critical Fixes
- `path/to/file:line` — {what was fixed}
## Warning Fixes
- `path/to/file:line` — {what was fixed}
## Skipped
- {finding reference} — {reason for skipping}
## Test Results
{Final test output confirming all pass}