Update issue bodies with RETRY feedback from issue-review-ready.
npx skills add https://github.com/apokamo/kaji --skill issue-fix-ready
Please help me install this Agent Skill. Skill: issue-fix-ready Source: https://github.com/apokamo/kaji/tree/main/.claude/skills/issue-fix-ready Command: npx skills add https://github.com/apokamo/kaji --skill issue-fix-ready
This guide helps update the Issue body to incorporate RETRY feedback from issue-review-ready, ensuring clear, actionable guidance for the next review cycle.
Update the Issue body to reflect RETRY feedback and commit the changes.
High-intent search queries and answers about installing and using this skill.
To update an issue body with RETRY feedback, fetch the issue content using kaji, parse the RETRY notes from review comments, and commit a revised description that addresses the requested clarification or added context.
A RETRY label in an issue-ready workflow indicates the issue requires clarification, rewording, or added context before it can proceed to re-review or close, based on feedback from the issue-review-ready stage.
You can extract RETRY points from the latest review comments and translate them into concrete edits, refreshing the issue's overview, objectives, and completion criteria to maintain consistent documentation.
Yes, you can use kaji to fetch the issue content, parse the RETRY notes left during the review-ready phase, and commit the revised description to prepare the issue for the next review cycle.
When applying RETRY feedback, maintain the existing issue structure—including overview, objectives, and completion criteria—while reflecting the new feedback to ensure consistent documentation for the team.
You should refresh an issue description after a review-ready cycle when the issue is labeled RETRY, requiring you to update the body with agreed action items so the team can resume from the correct context.
apokamoValidate Kaji workflows run via kaji run with stop-on-failure logging.
whatwecandoRevise project plans after architectural issues and detect orphan files.
silvarojasdiegoarturo91Analyze code structure and dependencies to generate module maps and caller diagrams.
paultyngGenerate prioritized PR review summaries and GitHub deep-linked comment drafts.
