Review the comments on a PR and address the findings that are valid and required.
npx skills add https://github.com/gjkim42/kanon-repo --skill address-pr-review見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Review the PR comments. Address the valid and required findings.
biwIntegrate the PR base, run persistent read-only reviewers, fix and re-review findings, validate with repo-native commands, address review bots, and compare model quality.
関連する理由: 開発
共通のキーワード: address · review · reviewers
robsonrungEvaluate pull request feedback against the code, apply valid fixes, and reply to or resolve the addressed threads. Use only when the user asks to address pull request feedback or review threads. Do not use to find new issues in a diff.
関連する理由: 開発
共通のキーワード: address · review · feedback
sjuneparkAddress existing GitHub PR feedback from human or bot reviewers end to end, including stacked PR chains.
関連する理由: 開発
共通のキーワード: address · reviewers · feedback
gjkim42Review the current Kelos branch, or an explicitly specified PR, issue, or diff, for Kubernetes API and CRD design quality. Use when asked for a Kelos API review, CRD/API compatibility review, Kubernetes API convention review, or review of changes under api/, generated CRDs, examples/, or self-development/ manifests. Default to the current branch when no target is specified. This skill is review-only.
gjkim42Sweep the current branch for leftovers of an abandoned design after a significant mid-work decision change, and rewrite the affected code, comments, tests, and docs so the result reads as if it had been designed this way from the beginning. Use when the user says "design cleanup", "clean up the old approach", "erase the journey", says a design decision changed and asks to clean up after it, or after a pivot in approach mid-branch. This is a rewrite pass over the code touched by the decision only
gjkim42Finish a PR by repeatedly requesting a Kelos review, waiting for its check, addressing valid review findings, squashing commits, and updating the PR until a review approves and that iteration is finalized. Use when the user says "finish-pr" or asks for this review-and-fix loop. Defaults to the PR for the current branch.
gjkim42Create and maintain gjkiminstruction.md, the root document for a loop-engineering effort. The document holds only the minimum requirements and confirmed decisions, and deliberately leaves everything else open so that later iterations are not locked into early guesses. Use whenever the user mentions gjkiminstruction.md, a root document or root doc for a loop, loop engineering, starting a long-running agent loop on a goal, or asks to record a requirement or a confirmed decision for such an effort.
