richkuo
Review Skills published by richkuo, their source repositories, maintenance signals, and identity status.
- Skills
- 4
- Repository stars
- 48
- Identity status
- Source-linked
Provenance
Source and identity
- Profile type
- Creator
- Canonical name
- richkuo
- Public sources
- 1
- License context
- MIT
Source entries
Agent Skills from richkuo
Repository stars and maintenance signals provide context, but do not automatically become an individual Skill's quality score.
richkuo/rk-skills
fix-pr-review-loop
Use when the user asks to fix a PR review and drive it to approval autonomously — "fix the PR review and loop until approved", "fix-pr-review-loop", "keep addressing review comments until this PR is approved", or as the standalone counterpart to work-on-issue-loop's polling/resolving steps for a PR that already exists. Takes an optional PR number/URL (defaults to the current branch's PR). Repeatedly calls fix-pr-review to resolve the latest review, waits for the resulting re-review from the sele
richkuo/rk-skills
fix-pr-review
Use when the user asks to fix, address, or respond to a PR review — "fix the PR review", "address the review comments", "/fix-pr-review". Takes an optional PR number/URL (defaults to the current branch's PR) and an optional `codex` argument, in either order, to select Codex as the review bot (e.g. "/fix-pr-review 123 codex"). Fetches every unaddressed review channel (formal reviews, review-style issue comments, inline diff threads, already-failed CI checks), RE-VALIDATES each finding against the
richkuo/rk-skills
prd-to-issues
Use when the user wants a finished PRD broken into GitHub milestones and issues — "file the issues from the PRD", "/prd-to-issues", "break this into GitHub issues". Derives dependency-ordered milestones, files complete complexity-scored issues (github-issue-format), and stamps each with an Execution block (typed predecessors, build model, effort, fableplan, plan effort, review trigger). Stage 4 of the new-app-pipeline.
richkuo/rk-skills
validate-issue
Use when the user asks to validate, review, or check whether a GitHub issue is valid. Accepts an issue reference or defaults to the latest open issue, verifies every factual claim against current code, assesses non-trivial proposals, scores complexity, and returns a cited update decision.
Pinned paths
Every entry links to a specific source path and commit when available.
Repository context
Activity, license, and repository-level popularity are shown as context.
Open the source
Inspect the public repository