How do I install the Develop Pr Coderabbit skill?

Run npx skillmds@latest add tegnike/develop-pr-coderabbit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Develop Pr Coderabbit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Develop Pr Coderabbit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Develop Pr Coderabbit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Develop Pr Coderabbit?

tegnike (@tegnike) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Develop Pr Coderabbit by tegnike — Agent Skill

Name: Develop Pr Coderabbit
Author: tegnike

Develop Pr Coderabbit

Use when creating or opening a GitHub pull request for a local repository where the PR should target develop, be ready for review, include a useful main PR body, and be checked for CodeRabbit feedback after creation.

tegnike a1f9702 2.2 KB Updated Sep 17, 2026

File contents

Develop PR + CodeRabbit

Workflow

Protect the current worktree.
- Read repository instructions first.
- Check git status --short --branch, current branch, remote, and git identity.
- Do not overwrite unrelated user changes.
Base the PR on develop.
- Fetch origin develop.
- Ensure the branch is based on the latest origin/develop, or rebase/merge with care before publishing.
- Use another base only when the user explicitly overrides this skill.
Verify before publishing.
- Run the repo-appropriate checks for the actual change.
- If a check cannot be run, record the reason for the PR body and final report.
Commit and push.
- Commit the intended change only.
- Push the current branch to the repository remote.
Create a ready PR.
- Use base branch develop.
- Create the PR as non-draft.
- Write the PR title, PR body, and any agent-authored PR comments or review replies in Japanese by default when the user conversation or repository instructions are Japanese. Keep commands, code identifiers, branch names, and tool-generated comments in their original language.
- The main PR comment/body must include:
  - Summary: concise bullets of what changed.
  - Verification: commands and browser/manual checks actually performed.
  - Notes: risks, dev-only behavior, or anything reviewers should know.
Wait for CodeRabbit.
- After PR creation, wait about 10 minutes for CodeRabbit to post feedback.
- Then inspect PR reviews, PR comments, and review threads from the live GitHub state.
Handle CodeRabbit feedback.
- If CodeRabbit feedback exists and is actionable, use the coderabbit-pr-review-resolver skill and follow that workflow.
- If no CodeRabbit feedback has arrived after the wait, report the exact check result instead of guessing.

Final Report

Report the branch, PR URL, base branch, commit SHA, checks run, and CodeRabbit status.

---name: develop-pr-coderabbitdescription: Use when creating or opening a GitHub pull request for a local repository where the PR should target develop, be ready for review, include a useful main PR body, and be checked for CodeRabbit feedback after creation.---# Develop PR + CodeRabbit## Workflow1. Protect the current worktree. - Read repository instructions first. - Check `git status --short --branch`, current branch, remote, and git identity. - Do not overwrite unrelated user changes.2. Base the PR on `develop`. - Fetch `origin develop`. - Ensure the branch is based on the latest `origin/develop`, or rebase/merge with care before publishing. - Use another base only when the user explicitly overrides this skill.3. Verify before publishing. - Run the repo-appropriate checks for the actual change. - If a check cannot be run, record the reason for the PR body and final report.4. Commit and push. - Commit the intended change only. - Push the current branch to the repository remote.5. Create a ready PR. - Use base branch `develop`. - Create the PR as non-draft. - Write the PR title, PR body, and any agent-authored PR comments or review replies in Japanese by default when the user conversation or repository instructions are Japanese. Keep commands, code identifiers, branch names, and tool-generated comments in their original language. - The main PR comment/body must include: - `Summary`: concise bullets of what changed. - `Verification`: commands and browser/manual checks actually performed. - `Notes`: risks, dev-only behavior, or anything reviewers should know.6. Wait for CodeRabbit. - After PR creation, wait about 10 minutes for CodeRabbit to post feedback. - Then inspect PR reviews, PR comments, and review threads from the live GitHub state.7. Handle CodeRabbit feedback. - If CodeRabbit feedback exists and is actionable, use the `coderabbit-pr-review-resolver` skill and follow that workflow. - If no CodeRabbit feedback has arrived after the wait, report the exact check result instead of guessing.## Final ReportReport the branch, PR URL, base branch, commit SHA, checks run, and CodeRabbit status.

Frequently asked questions