From openshift-developer
Fix code review findings before committing. Use when the user wants to address pre-commit review feedback, fix review findings in the current branch, or apply code review fixes and push.
How this skill is triggered — by the user, by Claude, or both
Slash command
/openshift-developer:address-review-precommitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
openshift-developer:address-review-precommit
openshift-developer:address-review-precommit
/openshift-developer:address-review-precommit
Applies code review findings to the current branch by editing the code, running verification, and pushing the fixes. Designed to run after /code-review:pre-commit-review to close the pre-PR author loop.
Parse the provided review findings and identify all actions and improvements that need to be addressed.
Address all actions and improvements by editing the code. For each finding:
Run verification to ensure nothing is broken:
make test 2>&1
make verify 2>&1
make verify generates new files, commit those too and run make verify again to confirm it passesgit push
/openshift-developer:address-review-precommit
The review findings are passed from the preceding /code-review:pre-commit-review output.git remote -v or git remote get-url originnpx claudepluginhub saschagrunert/ai-helpers --plugin openshift-developerGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
6plugins reuse this skill
First indexed Jul 11, 2026