New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Commit And PR Guidelines

by relytcloud in relytcloud/pg_ducklake

Commit message conventions and pull request description guidelines.

MITAuto-check: notesDevelopment

Install Commit And PR Guidelines

skills CLI
$ npx skills add relytcloud/pg_ducklake --skill commit-and-pr-guidelines -a claude-code

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

GitHub CLI
$ gh skill install relytcloud/pg_ducklake commit-and-pr-guidelines --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/relytcloud/pg_ducklake.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/commit-and-pr-guidelines .claude/skills/commit-and-pr-guidelines && 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/

Facts

Skill name
commit-and-pr-guidelines
GitHub stars
143
Token cost
~1.4k tokens
SKILL.md length
522 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Commit message conventions and pull request description guidelines.

  • Tasks that involve Commit messages
  • SKILL.md covers Format: Conventional Commits, Commit Types, Description and Body (Optional), plus 6 more sections
  • Calls git
  • Tasks that involve Pull requests

What it does

Commit And PR Guidelines is an agent skill from relytcloud/pg_ducklake. Commit message conventions and pull request description guidelines. Consult before every git commit or when creating or updating a pull request.

Its SKILL.md is about 1.4k 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 Commit messages and Pull requests. It works with PostgreSQL. The repository describes itself as: Native lakehouse experience in Postgres powered by DuckDB & Ducklake. The licence is MIT.

When your agent uses it

  • Tasks that involve Commit messages
  • Tasks that involve Pull requests

Example prompts

  • “/commit-and-pr-guidelines”

Requirements

  • Docker

What it can do on your machine

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

Commit And PR Guidelines loads about 1.4k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 522 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:184
    - Sensitive files (`.env`, `credentials.json`, API keys, passwords)

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 relytcloud/pg_ducklake at commit bc5d4b4, republished under its MIT licence (© relytcloud). 522 words, ~1,367 tokens.

Download SKILL.mdSave it as .claude/skills/commit-and-pr-guidelines/SKILL.md (or your agent's skills folder).
name
commit-and-pr-guidelines
description
Commit message conventions and pull request description guidelines. Consult before every git commit or when creating or updating a pull request.

Commit and Pull Request Guidelines

How to craft commit messages and pull request descriptions for the pg_ducklake repository.

Format: Conventional Commits

All commit messages MUST follow the Conventional Commits format:

<type>: <description>

[optional body]

Commit Types

Choose the appropriate type based on what changed:

  • feat: New feature or functionality
  • fix: Bug fix
  • docs: Documentation changes only
  • format: Code style formatting (whitespace, semicolons, etc.) - no logic changes
  • refactor: Code refactoring without changing behavior or fixing bugs
  • test: Adding or updating tests
  • chore: Maintenance tasks (dependencies, build config, tooling, etc.)
  • perf: Performance improvements
  • ci: CI/CD configuration changes (GitHub Actions, Docker builds, etc.)

Description

  • First line: Clear, concise summary (preferably under 50 characters)
  • Use imperative mood ("add" not "added" or "adds")
  • No period at the end
  • Lowercase after the colon

Good examples:

  • feat: add support for partitioned tables
  • fix: handle NULL values in UPDATE statements
  • ci: add ClickBench testing before release

Bad examples:

  • feat: Added new feature. (past tense, unnecessary period)
  • Fix bug (no scope, too vague)
  • Update code (not descriptive)

Body (Optional)

Use the body to explain:

  • What changed (if not obvious from the description)
  • Why the change was made (context, motivation)
  • How it was implemented (if the approach is non-obvious)
  • Any breaking changes or migration requirements

Wrap the body at 72 characters per line.

Examples

Simple feature addition
feat: add ALTER TABLE DROP COLUMN support

Implements column dropping for DuckLake tables via online schema
evolution. Updates metadata manager to handle column removal and
data file compaction.
Bug fix
fix: handle concurrent INSERT operations

Previously, concurrent INSERTs could cause metadata conflicts due to
race conditions. Now uses PostgreSQL XID-based locking to serialize
metadata updates.
CI/CD change
ci: add ClickBench testing before Docker image release

Ensures Docker images pass ClickBench benchmarks on all PostgreSQL
versions (14-18) and both architectures (amd64/arm64) before promotion
to production repository.
Documentation
docs: update compilation guide for macOS

Add instructions for Apple Silicon M1/M2 chips and clarify Xcode
command line tools requirements.
Chore/maintenance
chore: update pg_duckdb submodule to v0.3.0

Pulls in upstream fixes for DuckDB 1.2 compatibility.

How to Create the Commit

Before writing the commit message, analyze the changes:

bash
git status
git diff --staged
git diff

Also check recent commits to understand the project's patterns:

bash
git log --oneline -10

When committing, use a HEREDOC to ensure proper formatting:

bash
git commit -m "$(cat <<'EOF'
<type>: <description>

<optional body>
EOF
)"
Show full SKILL.md (272 more words)Show less

Pull Request Descriptions

Write pull request descriptions for human reviewers, not as exhaustive change logs. Keep them brief and focus on why the change is needed, along with context, tradeoffs, or design decisions that are not obvious from the diff. Do not hard-wrap prose paragraphs; keep each paragraph on one line.

Do not summarize code that reviewers can read in the diff. Omit routine testing sections when CI already provides the relevant result; mention testing only when manual or non-CI validation adds useful review context. Before creating or updating a pull request, inspect its complete commit range and diff against the target branch rather than describing only the latest commit.

End every pull request description with these unchecked items. Never check them on behalf of a human:

markdown
- [ ] This PR has been reviewed by human.
- [ ] This PR description has been reviewed by human.

Submodule Changes

When third_party/ducklake or the repo-root duckdb/ submodule is modified, commit the submodule pointer bump together with the pg_ducklake changes that depend on it. This keeps the change atomic -- the new export and its consumer land in one reviewable unit:

bash
git add third_party/ducklake <other dependent files>
git commit -m "<type>: <description>"

If the submodule update is unrelated to any pg_ducklake change (e.g., a pure upstream upgrade), commit it alone:

bash
git add third_party/ducklake
git commit -m "chore: bump ducklake to <version/reason>"

What NOT to Commit

Before committing, ensure you're not including:

  • Sensitive files (.env, credentials.json, API keys, passwords)
  • Large binary files (unless intentional)
  • Temporary files (.log, .tmp, compiled artifacts)
  • User-specific config (IDE settings, unless shared team config)

Use git add <specific-files> rather than git add -A to avoid accidentally staging unwanted files.

Git Safety Rules

  • NEVER amend commits unless explicitly requested by the user
  • NEVER force push to main/master branches
  • NEVER skip git hooks with --no-verify unless explicitly requested
  • NEVER create empty commits (unless using --allow-empty intentionally)

© relytcloud, MIT. 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/commit-and-pr-guidelines of relytcloud/pg_ducklake.

Open the folder on GitHubat commit bc5d4b4

Compare with similar skills

Commit And PR Guidelines 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.

Commit And PR Guidelines compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit And PR Guidelines this skillrelytcloud/pg_ducklake143—~1.4kAutomated safety check: NotesMIT
Git PR Flowwgzhao/Addax1.4k—~216Automated safety check: PassApache-2.0
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT

Similar skills

  • Git PR Flow

    wgzhao/Addax

    Standard branch, commit, and pull-request workflow for this repo.

    1.4k GitHub stars~216 tokensUpdated today
    DevelopmentAuto-check passed

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

    102k 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 today
    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 today
    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

More from relytcloud/pg_ducklake

  • Bump Up Ducklake

    relytcloud/pg_ducklake

    Safely bump pgducklake's vendored DuckLake commit, rebase its patch series, account for newly added upstream SQLLogicTests, update mapped test schedules, and validate the result.

    143 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Setup Dev

    relytcloud/pg_ducklake

    Dev environment setup for build tools, PostgreSQL, submodules, and worktrees.

    143 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check: notes

  • Version Management

    relytcloud/pg_ducklake

    Versioning, branch, and release policy (semantic versioning, branch-per-minor, tag-per-patch).

    143 GitHub stars~455 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Commit And PR Guidelines

What does Commit And PR Guidelines do?

Commit message conventions and pull request description guidelines. Commit And PR Guidelines is an agent skill from relytcloud/pg_ducklake. Commit message conventions and pull request description guidelines.

When should I use Commit And PR Guidelines?

Commit And PR Guidelines fits situations like: tasks that involve Commit messages; tasks that involve Pull requests.

How do I install Commit And PR Guidelines in Claude Code?

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

How do I install Commit And PR Guidelines in Codex?

Run `npx skills add relytcloud/pg_ducklake --skill commit-and-pr-guidelines -a codex`. Or copy the skill folder (.agents/skills/commit-and-pr-guidelines in relytcloud/pg_ducklake) into .agents/skills/commit-and-pr-guidelines in your project. Codex loads it when a task matches its description.

Can I use Commit And PR Guidelines 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 relytcloud/pg_ducklake --skill commit-and-pr-guidelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit-and-pr-guidelines, .gemini/skills/commit-and-pr-guidelines, .github/skills/commit-and-pr-guidelines and .opencode/skills/commit-and-pr-guidelines in your project.

What does Commit And PR Guidelines need to run?

Going by SKILL.md and its folder, Commit And PR Guidelines needs the command-line tools its instructions call (git). Our summary lists: Docker.

Does Commit And PR Guidelines 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 Commit And PR Guidelines safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Commit And PR Guidelines use?

Commit And PR Guidelines 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 Commit And PR Guidelines use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Commit And PR Guidelines?

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

Who maintains Commit And PR Guidelines?

relytcloud (a GitHub organization) maintains it in relytcloud/pg_ducklake, which has 143 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on August 26, 2026.

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