Agent skill

PR Submission Conventions

Sets the PR title and commit message format, pre-PR checks and PR body structure used when contributing to SkillHub.

Apache-2.0Auto-check passedDevelopment

Install PR Submission Conventions

skills CLI

$ npx skills add iflytek/skillhub --skill pr-submission -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install iflytek/skillhub pr-submission --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/iflytek/skillhub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pr-submission .claude/skills/pr-submission && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "pr-submission" agent skill from https://github.com/iflytek/skillhub/tree/main/.agents/skills/pr-submission into .claude/skills/pr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-submission", 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

$skill-installer install https://github.com/iflytek/skillhub/tree/main/.agents/skills/pr-submission

Type 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.

skills CLI

$ npx skills add iflytek/skillhub --skill pr-submission -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install iflytek/skillhub pr-submission --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iflytek/skillhub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/pr-submission .agents/skills/pr-submission && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "pr-submission" agent skill from https://github.com/iflytek/skillhub/tree/main/.agents/skills/pr-submission into .agents/skills/pr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-submission", 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.

skills CLI

$ npx skills add iflytek/skillhub --skill pr-submission -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install iflytek/skillhub pr-submission --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iflytek/skillhub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/pr-submission .cursor/skills/pr-submission && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "pr-submission" agent skill from https://github.com/iflytek/skillhub/tree/main/.agents/skills/pr-submission into .cursor/skills/pr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-submission", 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

$ gemini skills install https://github.com/iflytek/skillhub.git --path .agents/skills/pr-submission

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add iflytek/skillhub --skill pr-submission -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install iflytek/skillhub pr-submission --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iflytek/skillhub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/pr-submission .gemini/skills/pr-submission && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "pr-submission" agent skill from https://github.com/iflytek/skillhub/tree/main/.agents/skills/pr-submission into .gemini/skills/pr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-submission", 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.

GitHub CLI

$ gh skill install iflytek/skillhub pr-submission

Installs 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).

skills CLI

$ npx skills add iflytek/skillhub --skill pr-submission -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/iflytek/skillhub.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/pr-submission .github/skills/pr-submission && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "pr-submission" agent skill from https://github.com/iflytek/skillhub/tree/main/.agents/skills/pr-submission into .github/skills/pr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-submission", 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.

skills CLI

$ npx skills add iflytek/skillhub --skill pr-submission -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install iflytek/skillhub pr-submission --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iflytek/skillhub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/pr-submission .opencode/skills/pr-submission && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "pr-submission" agent skill from https://github.com/iflytek/skillhub/tree/main/.agents/skills/pr-submission into .opencode/skills/pr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-submission", 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-submission
GitHub stars: 5.2k
Token cost: ~793 tokens
SKILL.md length: 300 words
Files: 1
Skills in repo: 28
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Sets the PR title and commit message format, pre-PR checks and PR body structure used when contributing to SkillHub.

Works in 4 steps: Identify the scope of your change… → Format PR title and commits using the… → Run the pre-PR checklist commands → …
Naming a pull request or commit for the SkillHub repo
SKILL.md covers Workflow, PR Title Format, Commit Message Format and Pre-PR Checklist, plus 2 more sections
Calls make

What it does

Conventions for SkillHub contributions. Titles and commits follow conventional-commit style, type(scope): description, with the types feat, fix, docs, test, refactor and chore and scopes drawn from module names such as auth, search, publish, review, deploy, ci, frontend and scanner. One logical change goes in each commit.

A pre-PR checklist runs make test-backend-app, make typecheck-web and the make staging smoke test, plus make generate-api with the generated schema.d.ts committed when the API changed. Design docs are updated when APIs, auth flows or deployment change. The PR body then covers what changed, why, how, testing and impact.

When your agent uses it

Naming a pull request or commit for the SkillHub repo
Running the checklist before opening a PR
Reviewing a PR against the repo's conventions

Example prompts

“Write a PR title and description for my auth password-reset change.”
“Run the pre-PR checklist for this branch.”
“Check these commit messages against the SkillHub conventions.”

Requirements

A checkout of the SkillHub repository with its make targets

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Identify the scope of your change (feature, bug fix, docs, test, refactor, chore)
Format PR title and commits using the conventions below
Run the pre-PR checklist commands
Open the PR with a descriptive body

What it can do on your machine

Read from SKILL.md and the folder at commit 7352597. 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:
- make
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

PR Submission Conventions loads about 793 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 300 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~33
When it runs · the whole SKILL.md, loaded when a task matches: ~793

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 iflytek/skillhub at commit 7352597, republished under its Apache-2.0 licence (© iflytek). 300 words, ~793 tokens.

Download SKILL.mdSave it as .claude/skills/pr-submission/SKILL.md (or your agent's skills folder).

name: pr-submission
description: PR title format, commit conventions, and pre-PR checklist for SkillHub. Use when preparing or reviewing pull requests.
license: Apache-2.0

PR Submission Skill

Workflow

Identify the scope of your change (feature, bug fix, docs, test, refactor, chore)
Format PR title and commits using the conventions below
Run the pre-PR checklist commands
Open the PR with a descriptive body

PR Title Format

Use conventional commit style:

<type>(<scope>): <description>

Types:

Type	When to Use
`feat`	New feature or capability
`fix`	Bug fix
`docs`	Documentation changes only
`test`	Adding or updating tests
`refactor`	Code restructuring with no behavior change
`chore`	Build, CI, tooling, or maintenance tasks

Scopes: Use module or domain names: auth, search, publish, review, namespace, governance, deploy, ci, frontend, scanner

Examples:

feat(auth): add local account login with password reset
fix(publish): resolve null pointer when skill metadata is missing name
docs(deploy): clarify runtime image usage
test(namespace): add membership service edge case tests
refactor(review): extract query repository for governance list
chore(ci): add parallel workflow scripts for multi-agent development

Commit Message Format

Same convention as PR titles. One logical change per commit.

Types:

feat: A new feature for the user
fix: A bug fix for the user
docs: Documentation changes only
test: Adding or updating tests
refactor: Code change that neither fixes a bug nor adds a feature
chore: Changes to build process, CI, or maintenance tasks

Examples:

fix(auth): resolve session cookie conflict in device flow
feat(publish): support security scan before review submission
docs(skill-protocol): add nested SKILL.md discovery rules
test(search): verify jieba analysis with Chinese skill descriptions
refactor(storage): simplify LocalFile path normalization

Pre-PR Checklist

Backend tests pass: make test-backend-app
Frontend typecheck passes: make typecheck-web
If API changed: make generate-api was run and web/src/api/generated/schema.d.ts is committed
Smoke test passes: make staging
Follow existing module boundaries and dependency direction
Add/update tests for new behavior
Update design docs when APIs, auth flows, deployment, or operator workflows change

PR Body Structure

When creating a PR, include:

What — Summary of the change
Why — Motivation (link to issue if applicable)
How — Key implementation details (especially for non-obvious decisions)
Testing — How to verify the change works
Impact — Breaking changes, migration notes, or rollout considerations

Review Conventions

When reviewing, cite the specific AGENTS.md rule that applies if suggesting a convention change
For backend code, check dependency direction does not violate clean architecture rules
For frontend code, check OpenAPI types are regenerated if API changed

Files

Just SKILL.md in .agents/skills/pr-submission of iflytek/skillhub.

Open the folder on GitHubat commit 7352597

Compare with similar skills

PR Submission Conventions 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.

PR Submission Conventions compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
PR Submission Conventions this skilliflytek/skillhub	5.2k	—	~793	Automated safety check: Pass	Apache-2.0	today
PR Finalize Reviewmicrosoft/garnet	12k	—	~3.1k	Automated safety check: Pass	MIT	today
Git Workflow and Versioningaddyosmani/agent-skills	103k	2 repos	~3.5k	Automated safety check: Notes	MIT	5 days ago
React Router Pull Request Creatorremix-run/react-router	57k	—	~2.5k	Automated safety check: Pass	MIT	2 days ago
Verdaccio Pull Request Workflowverdaccio/verdaccio	18k	—	~1.9k	Automated safety check: Pass	MIT	2 days ago
Emoji Commit ConventionsbaptisteArno/typebot.io	11k	—	~424	Automated safety check: Pass	Custom licence	yesterday

Similar skills

PR Finalize Review
microsoft/garnet
Official
Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.
12k GitHub stars~3.1k tokensUpdated today
DevelopmentAuto-check passed
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
103k GitHub starsUsed in 2 repos~3.5k tokens
DevelopmentAuto-check: notes
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
57k GitHub stars~2.5k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
18k GitHub stars~1.9k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Emoji Commit Conventions
baptisteArno/typebot.io
Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.
11k GitHub stars~424 tokensUpdated yesterday
DevelopmentAuto-check passed
Commit And PR Messages
superplanehq/superplane
Write Git commit messages and pull request titles/descriptions using the Chris Beams / Tim Pope conventions (subject/body split, ~50-char subject, imperative mood, why-not-how body) plus ASD-STE100…
7.7k GitHub stars~1.6k tokensUpdated today
DevelopmentAuto-check passed

Questions about PR Submission Conventions

What does PR Submission Conventions do?

Sets the PR title and commit message format, pre-PR checks and PR body structure used when contributing to SkillHub. Conventions for SkillHub contributions. Titles and commits follow conventional-commit style, type(scope): description, with the types feat, fix, docs, test, refactor and chore and scopes drawn from module names such as auth, search, publish, review, deploy, ci, frontend and scanner.

When should I use PR Submission Conventions?

PR Submission Conventions fits situations like: naming a pull request or commit for the SkillHub repo; running the checklist before opening a PR; reviewing a PR against the repo's conventions.

How do I install PR Submission Conventions in Claude Code?

Run `npx skills add iflytek/skillhub --skill pr-submission -a claude-code`. Or copy the skill folder (.agents/skills/pr-submission in iflytek/skillhub) into .claude/skills/pr-submission in your project. Claude Code loads it when a task matches its description.

How do I install PR Submission Conventions in Codex?

Run `npx skills add iflytek/skillhub --skill pr-submission -a codex`. Or copy the skill folder (.agents/skills/pr-submission in iflytek/skillhub) into .agents/skills/pr-submission in your project. Codex loads it when a task matches its description.

Can I use PR Submission Conventions 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 iflytek/skillhub --skill pr-submission -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-submission, .gemini/skills/pr-submission, .github/skills/pr-submission and .opencode/skills/pr-submission in your project.

What does PR Submission Conventions need to run?

Going by SKILL.md and its folder, PR Submission Conventions needs the command-line tools its instructions call (make). Our summary lists: A checkout of the SkillHub repository with its make targets.

Does PR Submission Conventions 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 PR Submission Conventions 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 Submission Conventions use?

PR Submission Conventions is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PR Submission Conventions use?

About 793 tokens (SKILL.md is roughly 3.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 Submission Conventions?

Skills that share tags, products or a category with PR Submission Conventions: PR Finalize Review (microsoft/garnet, 12k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Submission Conventions?

iflytek (a GitHub organization) maintains it in iflytek/skillhub, which has 5,157 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 8, 2026.

Source: iflytek/skillhub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install PR Submission Conventions

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

PR Submission Skill

Workflow

PR Title Format

Commit Message Format

Pre-PR Checklist

PR Body Structure

Review Conventions

Files

Compare with similar skills

Similar skills

More from iflytek/skillhub

Related

Questions about PR Submission Conventions