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.
Audits and improves GitHub repository quality — README structure, community health files, .github directory setup, issue/PR templates, metadata, releases, and branch hygiene.
Install GitHub Repo
$ npx skills add jdevalk/skills --skill github-repo -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jdevalk/skills github-repo --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/jdevalk/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/github-repo .claude/skills/github-repo && 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 "github-repo" agent skill from https://github.com/jdevalk/skills/tree/main/github-repo into .claude/skills/github-repo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-repo", 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/jdevalk/skills/tree/main/github-repoType 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 jdevalk/skills --skill github-repo -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jdevalk/skills github-repo --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdevalk/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/github-repo .agents/skills/github-repo && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "github-repo" agent skill from https://github.com/jdevalk/skills/tree/main/github-repo into .agents/skills/github-repo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-repo", 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 jdevalk/skills --skill github-repo -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jdevalk/skills github-repo --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdevalk/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/github-repo .cursor/skills/github-repo && 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 "github-repo" agent skill from https://github.com/jdevalk/skills/tree/main/github-repo into .cursor/skills/github-repo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-repo", 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/jdevalk/skills.git --path github-repo--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 jdevalk/skills --skill github-repo -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jdevalk/skills github-repo --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdevalk/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/github-repo .gemini/skills/github-repo && 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 "github-repo" agent skill from https://github.com/jdevalk/skills/tree/main/github-repo into .gemini/skills/github-repo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-repo", 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 jdevalk/skills github-repoInstalls 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 jdevalk/skills --skill github-repo -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jdevalk/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/github-repo .github/skills/github-repo && 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 "github-repo" agent skill from https://github.com/jdevalk/skills/tree/main/github-repo into .github/skills/github-repo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-repo", 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 jdevalk/skills --skill github-repo -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jdevalk/skills github-repo --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdevalk/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/github-repo .opencode/skills/github-repo && 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 "github-repo" agent skill from https://github.com/jdevalk/skills/tree/main/github-repo into .opencode/skills/github-repo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-repo", 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
github-repo- GitHub stars
- 104
- Token cost
- ~1.5k tokens
- SKILL.md length
- 661 words
- Files
- 4
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
Audits and improves GitHub repository quality — README structure, community health files, .github directory setup, issue/PR templates, metadata, releases, and branch hygiene.
- Works in 5 steps: Gather Context → Audit → Generate or Improve Files → …
- The user asks to improve
- SKILL.md covers Workflow, Phase 0: Gather Context, Phase 1: Audit and Phase 2: Generate or Improve…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
GitHub Repo is an agent skill from jdevalk/skills. Audits and improves GitHub repository quality — README structure, community health files, .github directory setup, issue/PR templates, metadata, releases, and branch hygiene. Use this skill whenever the user asks to improve, audit, review, or set up a GitHub repository, or when they mention things like "make my repo look professional", "add contributing guidelines", "set up issue templates", "improve my README", "clean up my repo", "prepare my repo for open source", or "make my GitHub project look good". Also…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `AGENTS.md`, `README.md` and `evals/evals.json`).
It sits in Development, covering Open source maintenance, Technical documentation and Policy and terms drafting. It works with GitHub and Git. The repository describes itself as: Agent skills for GitHub repos and profiles, WordPress and EmDash plugins, Astro SEO, and content readability. The licence is MIT.
When your agent uses it
- The user asks to improve
- Set up a GitHub repository
- They mention things like make my repo look professional
- Add contributing guidelines
Example prompts
- “make my repo look professional”
- “add contributing guidelines”
- “set up issue templates”
- “/github-repo”
Workflow steps
5 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 106fc68. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
GitHub Repo loads about 1.5k tokens when it runs. Until then it costs about 208 tokens; SKILL.md has 661 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 jdevalk/skills at commit 106fc68, republished under its MIT licence (© jdevalk). 661 words, ~1,498 tokens.
Download SKILL.mdSave it as
.claude/skills/github-repo/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- github-repo
- description
- Audits and improves GitHub repository quality — README structure, community health files, .github directory setup, issue/PR templates, metadata, releases, and branch hygiene. Use this skill whenever the user asks to improve, audit, review, or set up a GitHub repository, or when they mention things like "make my repo look professional", "add contributing guidelines", "set up issue templates", "improve my README", "clean up my repo", "prepare my repo for open source", or "make my GitHub project look good". Also trigger when working inside a git repository and the user asks about best practices for documentation, community files, or repository structure. If the user is in a repo directory and mentions README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT, LICENSE, .github, templates, or release tags, use this skill.
GitHub Repository Optimizer
This skill audits a GitHub repository against best practices and generates or improves the files that make a repo look professional, welcoming, and well-maintained. It works with live repos (via gh CLI), local git directories, or files the user provides.
Implementation recipes live in AGENTS.md — read it when you need to generate or improve specific files. This file has the workflow and audit checklist.
Workflow
- Gather repo context — Determine what we're working with and collect information
- Run the audit — Score every aspect of the repo's public-facing quality
- Generate or improve files — Produce the files that are missing or need work. Recipes are in
AGENTS.md. - Metadata and readability pass — invoke
metadata-checkon the repo description and README blurb;readability-checkon prose-heavy files. - Verify — Confirm the outputs are correct and complete
Phase 0: Gather Context
Key information to collect: repo name, description, language/framework, README existence and quality, which community health files exist, issue/PR template status, CI/CD status, release history, branch count. Use gh CLI if authenticated, otherwise read local files.
Phase 1: Audit
Score each category out of 10. For each, give 2–4 specific findings that quote the actual state.
README Quality (x/10)
Does the README exist? Is it well-structured with: project name and clear one-liner, badge row (build/license/version), description explaining what/why/who, quick start (install + first use in 3 steps or fewer), code examples, screenshots/demos if visual, configuration docs, contributing link, license mention? Is it under 500 lines with <details> for optional content?
Repository Metadata (x/10)
- Description set and useful (not blank or "My awesome project")?
- Topics/tags relevant and complete?
- Website URL set if applicable?
- Social preview image uploaded?
- "Packages", "Environments", "Deployments" sections hidden if unused?
Community Health Files (x/10)
- CONTRIBUTING.md — exists? Covers dev setup, code style, testing, PR process?
- SECURITY.md — exists? Directs to private reporting channel, states response time?
- CODE_OF_CONDUCT.md — exists? Contributor Covenant 2.1 is the standard.
- LICENSE — exists in root? Appropriate for project type?
- SUPPORT.md — exists? Separates bugs from support questions?
- CHANGELOG.md — follows Keep a Changelog format?
For organizations: check for a .github repository with org-wide default health files.
Issue & PR Templates (x/10)
- YAML-based issue forms (
.github/ISSUE_TEMPLATE/*.yml) with at least bug report and feature request? Numbered filenames for ordering? config.ymldisabling blank issues and linking external support?- PR template with description, related issues (
Closes #XXX), type-of-change checkboxes, testing checklist? - CODEOWNERS file defining reviewers per directory?
Show full SKILL.md (268 more words)Show less
CI/CD & Automation (x/10)
- GitHub Actions workflows for testing, linting, building? Passing status badges in README?
- Dependabot or Renovate configured?
- Code quality (CodeQL, linting actions)?
- Stale issue management?
Releases & Branch Hygiene (x/10)
- Tagged releases with changelogs? Semantic versioning?
- Stale branches cleaned up?
.gitattributeswithexport-ignore?- Auto-release (semantic-release or release-please)?
Phase 2: Generate or Improve Files
Based on the audit, generate the files that are missing or need improvement. Always ask before overwriting. Read AGENTS.md for detailed recipes.
File generation order by impact: README.md, LICENSE, CONTRIBUTING.md, SECURITY.md, CODE_OF_CONDUCT.md, issue templates, PR template, CHANGELOG.md, SUPPORT.md, config files (dependabot.yml, CODEOWNERS, FUNDING.yml).
AGENTS.md sections: README generation, Community health files (CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), Issue templates, Organization-level setup (.github repo, org profile, private member profile, domain verification, rulesets).
Phase 2.5: Metadata and readability pass
- Metadata pass —
metadata-checkskill. Run on the repo description (first ~100 chars show in search and profile cards) and the README's opening blurb. - Prose pass —
readability-checkskill. Run on every prose-heavy file — at minimum the README, plus CONTRIBUTING.md and SECURITY.md if you produced them.
Apply fixes directly. Skip for code-heavy files (issue templates, workflow YAML).
Phase 3: Verify
- Verify files are in the correct locations.
- Check that all internal links in the README work.
- Confirm badge URLs are correctly formatted.
- If
ghis available, remind the user to update the repo's About section (description, topics, website URL, social preview) — these can't be set via files alone. - Summarize what was created/changed and what the user should do next.
Output format
Score table (6 categories, x/60), grouped findings quoting actual state, list of files generated/changed, and next steps for the user.
© jdevalk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files in github-repo of jdevalk/skills.
- SKILL.md
- AGENTS.md
- README.md
- evals/evals.json
Open the folder on GitHubat commit 106fc68
Compare with similar skills
GitHub Repo 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 |
|---|---|---|---|---|---|---|
| GitHub Repo this skilljdevalk/skills | 104 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Mole Release Notes Publishertw93/Mole | 69k | — | ~1.9k | Automated safety check: Pass | GPL-3.0 | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Ansible Backport Creatoransible/ansible | 71k | — | ~1.2k | Automated safety check: Pass | GPL-3.0 | |
| RTK Issue Triagertk-ai/rtk | 83k | — | ~3k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
Ansible Backport Creator
ansible/ansible
Creates backports of a merged Ansible devel pull request onto the right stable branches by cherry-picking its merge commit onto new backport branches.
RTK Issue Triage
rtk-ai/rtk
Audits open GitHub issues, categorizes them, flags duplicates and linked PRs in three phases, with optional deep analysis and comments posted only after validation.
- Official
Open-Source Release Readiness
trailofbits/skills
Walks a repository through release readiness before it goes public: secrets audit, licensing, documentation, CI and language-specific packaging.
More from jdevalk/skills
All 9 skills in this repoWp Static Clone
jdevalk/skills
Clones a live WordPress (or other CMS-driven) site into a static HTML site deployable on any static host (Cloudflare Pages, Netlify, Vercel, S3+CloudFront, plain Apache/nginx).
Astro SEO
jdevalk/skills
Audits and improves SEO for Astro sites. An agent skill from jdevalk/skills.
Content SEO
jdevalk/skills
Audits a blog post draft or page copy for content-level SEO: search intent fit, focus keyphrase placement, E-E-A-T signals (experience, expertise, authoritativeness, trustworthiness), helpfulness…
Metadata Check
jdevalk/skills
Reviews short high-value strings — page titles, meta descriptions, schema description fields, FAQ answers, GitHub repo taglines, profile bios, social-card copy, and other metadata where Flesch and…
Readability Check
jdevalk/skills
Runs a readability audit on a blog post draft or other multi-paragraph prose, calibrated for readers who read English as a second language.
Static SEO
jdevalk/skills
Audits and improves SEO for static HTML sites. An agent skill from jdevalk/skills.
Related
Categories
Questions about GitHub Repo
What does GitHub Repo do?
Audits and improves GitHub repository quality — README structure, community health files, .github directory setup, issue/PR templates, metadata, releases, and branch hygiene. GitHub Repo is an agent skill from jdevalk/skills.github directory setup, issue/PR templates, metadata, releases, and branch hygiene.
When should I use GitHub Repo?
GitHub Repo fits situations like: the user asks to improve; set up a GitHub repository; they mention things like make my repo look professional; add contributing guidelines.
How do I install GitHub Repo in Claude Code?
Run `npx skills add jdevalk/skills --skill github-repo -a claude-code`. Or copy the skill folder (github-repo in jdevalk/skills) into .claude/skills/github-repo in your project. Claude Code loads it when a task matches its description.
How do I install GitHub Repo in Codex?
Run `npx skills add jdevalk/skills --skill github-repo -a codex`. Or copy the skill folder (github-repo in jdevalk/skills) into .agents/skills/github-repo in your project. Codex loads it when a task matches its description.
Can I use GitHub Repo 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 jdevalk/skills --skill github-repo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-repo, .gemini/skills/github-repo, .github/skills/github-repo and .opencode/skills/github-repo in your project.
What does GitHub Repo need to run?
SKILL.md names no scripts, command-line tools or credentials: GitHub Repo is instructions for the agent only.
Does GitHub Repo access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is GitHub Repo 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 GitHub Repo use?
GitHub Repo is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does GitHub Repo use?
About 1.5k tokens (SKILL.md is roughly 6k 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 GitHub Repo?
Skills that share tags, products or a category with GitHub Repo: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Mole Release Notes Publisher (tw93/Mole, 69k stars), Pre-Release PR Triage (jamiepine/voicebox, 57k stars) and Ansible Backport Creator (ansible/ansible, 71k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GitHub Repo?
jdevalk (a GitHub user) maintains it in jdevalk/skills, which has 104 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on July 5, 2026.
Source: jdevalk/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.