Gitshot Image Uploader
trekawek/coffee-gb
Uploads screenshots and other images from the terminal and returns markdown-ready URLs to embed in GitHub pull requests, issues and comments.
Reviews GitHub Pull Requests/Merge Requests and generates a clean, actionable GitHub Flavored Markdown (GFM) checklist of requested changes.
Install PR Change Requester
$ npx skills add nekomangaorg/Neko --skill pr-change-requester -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nekomangaorg/Neko pr-change-requester --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nekomangaorg/Neko.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prchanger .claude/skills/pr-change-requester && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pr-change-requester" agent skill from https://github.com/nekomangaorg/Neko/tree/main/.agents/skills/prchanger into .claude/skills/pr-change-requester/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-change-requester", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nekomangaorg/Neko/tree/main/.agents/skills/prchangerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nekomangaorg/Neko --skill pr-change-requester -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nekomangaorg/Neko pr-change-requester --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nekomangaorg/Neko.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/prchanger .agents/skills/pr-change-requester && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pr-change-requester" agent skill from https://github.com/nekomangaorg/Neko/tree/main/.agents/skills/prchanger into .agents/skills/pr-change-requester/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-change-requester", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nekomangaorg/Neko --skill pr-change-requester -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nekomangaorg/Neko pr-change-requester --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nekomangaorg/Neko.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/prchanger .cursor/skills/pr-change-requester && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pr-change-requester" agent skill from https://github.com/nekomangaorg/Neko/tree/main/.agents/skills/prchanger into .cursor/skills/pr-change-requester/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-change-requester", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nekomangaorg/Neko.git --path .agents/skills/prchanger--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nekomangaorg/Neko --skill pr-change-requester -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nekomangaorg/Neko pr-change-requester --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nekomangaorg/Neko.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/prchanger .gemini/skills/pr-change-requester && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pr-change-requester" agent skill from https://github.com/nekomangaorg/Neko/tree/main/.agents/skills/prchanger into .gemini/skills/pr-change-requester/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-change-requester", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nekomangaorg/Neko pr-change-requesterInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nekomangaorg/Neko --skill pr-change-requester -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nekomangaorg/Neko.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/prchanger .github/skills/pr-change-requester && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pr-change-requester" agent skill from https://github.com/nekomangaorg/Neko/tree/main/.agents/skills/prchanger into .github/skills/pr-change-requester/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-change-requester", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nekomangaorg/Neko --skill pr-change-requester -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nekomangaorg/Neko pr-change-requester --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nekomangaorg/Neko.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/prchanger .opencode/skills/pr-change-requester && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pr-change-requester" agent skill from https://github.com/nekomangaorg/Neko/tree/main/.agents/skills/prchanger into .opencode/skills/pr-change-requester/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-change-requester", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pr-change-requester- GitHub stars
- 2.8k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 455 words
- Files
- 1
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Reviews GitHub Pull Requests/Merge Requests and generates a clean, actionable GitHub Flavored Markdown (GFM) checklist of requested changes.
- Works in 4 steps: 🚨 Correctness & Bugs → 🧪 Test Coverage & Edge Cases → 🧹 Maintainability & Readability → …
- You need a clear
- SKILL.md covers ✅ Always do:, ⚠️ Ask first: and 🚫 Never do:
- Calls git
What it does
PR Change Requester is an agent skill from nekomangaorg/Neko. Reviews GitHub Pull Requests/Merge Requests and generates a clean, actionable GitHub Flavored Markdown (GFM) checklist of requested changes. Use this skill when you need a clear, easy-to-understand review summary that developers can copy directly into a PR review, issue, or markdown file.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests and Markdown. It works with GitHub. The repository describes itself as: Unofficial MangaDex Reader for Android 8+. The licence is Apache-2.0.
When your agent uses it
- You need a clear
- Easy-to-understand review summary that developers can copy directly into a PR review
Example prompts
- “Use the pr-change-requester skill to review GitHub Pull Requests/Merge Requests and generates a clean, actionable GitHub Flavored Markdown (GFM)…”
- “/pr-change-requester”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e52cc82. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
PR Change Requester loads about 1.3k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 455 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from nekomangaorg/Neko at commit e52cc82, republished under its Apache-2.0 licence (© nekomangaorg). 455 words, ~1,304 tokens.
Download SKILL.mdSave it as
.claude/skills/pr-change-requester/SKILL.md (or your agent's skills folder).- name
- pr-change-requester
- description
- Reviews GitHub Pull Requests/Merge Requests and generates a clean, actionable GitHub Flavored Markdown (GFM) checklist of requested changes. Use this skill when you need a clear, easy-to-understand review summary that developers can copy directly into a PR review, issue, or markdown file.
Goal
You are "The PR Review Partner" 📋✨ — an empathetic, pragmatic code reviewer focused on clarity and actionable feedback. Your mission is to inspect a GitHub Pull Request (or GitLab Merge Request), identify bugs, missing test coverage, logic errors, and style regressions, and produce a GitHub Flavored Markdown (.md) report containing a concise, easy-to-digest checklist of requested changes.
Philosophy:
- "Reviews should unblock, not interrogate."
- "Every requested change must be concrete and actionable."
- "Clarity and developer experience beat long-winded essays."
- "Group feedback by priority so authors know what blocks merge versus what is optional."
Constraints
✅ Always do:
- Output results strictly in valid GitHub Flavored Markdown (GFM).
- Use GitHub task lists (
- [ ]) for all requested changes so the author can check items off directly in the UI. - Use GitHub Markdown alert callouts (
> [!WARNING],> [!NOTE],> [!TIP]) to highlight important context. - Include file paths and line numbers (or GitHub permalinks/diff references) for every item.
- Provide quick "Before / After" code snippets or concrete replacement suggestions where applicable.
- Classify feedback clearly into Blockers (Must Fix), Improvements (Should Fix), and Nits / Suggestions (Nice to Have).
⚠️ Ask first:
- If the user wants to automatically save the markdown content into a specific file (e.g.,
CHANGES_REQUESTED.mdor.github/pr-feedback.md). - If there is an existing project style guide or review template they want to conform to.
🚫 Never do:
- Overwhelm the author with wall-of-text explanations without clear action items.
- Use vague criticism like "clean this up" or "rethink this logic" without suggesting a solution.
- Include unverified file paths or fabricate line numbers.
- Block PRs on subjective aesthetic preferences that are not backed by repo conventions or lint rules.
Review Dimensions
Scan the MR/PR diff systematically across four practical dimensions:
Show full SKILL.md (181 more words)Show less
1. 🚨 Correctness & Bugs
- Unhandled
null,undefined, or empty collection errors. - Off-by-one errors, broken boundary conditions, or inverted conditional logic.
- Race conditions, missing locks, or unhandled async rejections/exceptions.
2. 🧪 Test Coverage & Edge Cases
- Missing unit or integration tests for newly introduced business logic.
- Happy-path-only tests that miss edge cases, timeouts, or failure modes.
- Flaky test patterns or brittle mock assertions.
3. 🧹 Maintainability & Readability
- Overly complex methods that can be split into readable helpers.
- Misleading variable or function names.
- Dead code, dangling debugging statements, or leftover
console.log/printlncalls.
4. ⚡ Performance & Resource Leaks
- Redundant API calls, N+1 query patterns, or unindexed lookups.
- Unclosed connections, streams, or listeners.
Instructions
- DIFF INSPECTION: Review the changes introduced in the PR/MR diff (
git diff target..HEADor provided patch). - FILTER & GROUP: Distinguish between merge-blocking bugs, recommended improvements, and optional nits.
- GENERATE MARKDOWN: Format the entire review into clean GitHub Flavored Markdown using the structure below.
- SAVE (Optional): If requested by the user, write the content directly to a markdown file in the repository (e.g.,
pr-review-feedback.md).
Output Format
Produce the review using the following GFM template:
# 🔍 Pull Request Review: Changes Requested
> [!WARNING]
> **Status:** Changes Requested
> **Summary:** [1–2 sentences summarizing the state of the PR and main goals of these changes]
---
## 🛑 Must Fix (Blockers)
*Issues that introduce bugs, regressions, or security/correctness flaws.*
- [ ] **`path/to/file.ext` (L42-L48)**: Fix potential `null` pointer when payload is empty.
- **Issue:** Accessing `.data` directly without checking if `response` succeeded.
- **Suggested Change:**
```language
// Suggested fix:
if (response?.data != null) { ... }
```
---
## ⚠️ Should Fix (Improvements)
*Gaps in testing, error handling, or architecture that should be addressed before merging.*
- [ ] **`path/to/test_file.ext`**: Add missing unit tests for failure state.
- **Suggested Change:** Add a test covering what happens when the network call returns a 500 status.
---
## 💡 Nice to Have (Suggestions / Nits)
*Non-blocking optimizations, naming improvements, or code hygiene.*
- [ ] **`path/to/file.ext` (L12)**: Remove unused import `import foo.bar.Baz`.
- [ ] **`path/to/file.ext` (L88)**: Consider renaming `calcData()` to `calculateBillingMetrics()` for clarity.
---
## 📋 Action Checklist Summary
- [ ] Resolve blocker items
- [ ] Address improvement suggestions
- [ ] Verify local tests pass (`npm test` / `./gradlew test` / `pytest`)© nekomangaorg, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/prchanger of nekomangaorg/Neko.
Open the folder on GitHubat commit e52cc82
Compare with similar skills
PR Change Requester next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| PR Change Requester this skillnekomangaorg/Neko | 2.8k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Gitshot Image Uploadertrekawek/coffee-gb | 1.2k | — | ~855 | Automated safety check: Pass | MIT | |
| Markdown Without Hard Wrapsprisma/orm | 48k | — | ~472 | Automated safety check: Pass | Apache-2.0 | |
| Submit Integrationlangchain-ai/docs | 426 | — | ~1.3k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
Markdown Without Hard Wraps
prisma/orm
Keeps Markdown prose on one line per paragraph instead of wrapping at a fixed column, so renderers can reflow it and diffs stay clean.
- Official
Submit Integration
langchain-ai/docs
Create a LangChain docs integration listing from a structured GitHub issue submission (issue form fields as JSON).
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
More from nekomangaorg/Neko
All 15 skills in this repoArchitecture Overclock
nekomangaorg/Neko
Resolves deep, structural performance bottlenecks in the Kotlin Android codebase.
Architecture Renovator
nekomangaorg/Neko
Resolves deep architectural debt in the Kotlin Android codebase through macro-level refactoring.
Build Foreman
nekomangaorg/Neko
Optimizes Gradle build scripts, compilation times, and Android Studio sync performance.
Code Steward
nekomangaorg/Neko
Maintains Kotlin codebase health, idiomatic style, and modern API usage.
Domain Distiller
nekomangaorg/Neko
Extracts duplicated or tangled business logic from ViewModels, Repositories, or UI components into pure, highly testable Kotlin Use Cases (Interactors) following the Single Responsibility Principle.
Frontend Artisan
nekomangaorg/Neko
Elevates the Jetpack Compose user interface through micro-UX improvements, animations, accessibility (a11y) fixes, and UI structural polish.
Related
Works with
Categories
Questions about PR Change Requester
What does PR Change Requester do?
Reviews GitHub Pull Requests/Merge Requests and generates a clean, actionable GitHub Flavored Markdown (GFM) checklist of requested changes. PR Change Requester is an agent skill from nekomangaorg/Neko. Reviews GitHub Pull Requests/Merge Requests and generates a clean, actionable GitHub Flavored Markdown (GFM) checklist of requested changes.
When should I use PR Change Requester?
PR Change Requester fits situations like: you need a clear; easy-to-understand review summary that developers can copy directly into a PR review.
How do I install PR Change Requester in Claude Code?
Run `npx skills add nekomangaorg/Neko --skill pr-change-requester -a claude-code`. Or copy the skill folder (.agents/skills/prchanger in nekomangaorg/Neko) into .claude/skills/pr-change-requester in your project. Claude Code loads it when a task matches its description.
How do I install PR Change Requester in Codex?
Run `npx skills add nekomangaorg/Neko --skill pr-change-requester -a codex`. Or copy the skill folder (.agents/skills/prchanger in nekomangaorg/Neko) into .agents/skills/pr-change-requester in your project. Codex loads it when a task matches its description.
Can I use PR Change Requester in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nekomangaorg/Neko --skill pr-change-requester -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-change-requester, .gemini/skills/pr-change-requester, .github/skills/pr-change-requester and .opencode/skills/pr-change-requester in your project.
What does PR Change Requester need to run?
Going by SKILL.md and its folder, PR Change Requester needs the command-line tools its instructions call (git).
Does PR Change Requester access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is PR Change Requester safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does PR Change Requester use?
PR Change Requester is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does PR Change Requester use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to PR Change Requester?
Skills that share tags, products or a category with PR Change Requester: Gitshot Image Uploader (trekawek/coffee-gb, 1.2k stars), Markdown Without Hard Wraps (prisma/orm, 48k stars), Submit Integration (langchain-ai/docs, 426 stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains PR Change Requester?
nekomangaorg (a GitHub organization) maintains it in nekomangaorg/Neko, which has 2,812 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 9, 2026.
Source: nekomangaorg/Neko on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.