Creating Pull Requests

OrganizationPopular

lightdash

creating-pull-requests

Use when creating, opening, or writing the title/description of a pull request, or writing PR bodies via `gh pr create` or `gt submit`. Covers what must go in the PR description (a ticket — GitHub issue or Linear) and what must never appear (client/customer names or their data).

Overview

Publisher	lightdash
Repository	`lightdash`
Skill name	`creating-pull-requests`
Stars	6.2K
Forks	790
Bundled files	Instructions only
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by lightdash on GitHub. Read the source before you install it.

Installation

Install the Creating Pull Requests AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/lightdash/lightdash/tree/main/.claude/skills/creating-pull-requests
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/lightdash/lightdash.git /tmp/lightdash
mkdir -p .claude/skills
cp -r /tmp/lightdash/.claude/skills/creating-pull-requests .claude/skills/creating-pull-requests

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Creating Pull Requests in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Creating Pull Requests on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Creating Pull Requests is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Creating Pull Requests

Conventions for every PR body in this repo. Applies regardless of whether the PR is opened via gh pr create or gt submit.

Rules

PR titles must be conventional commits — <type>[optional scope]: <description>, with a type from build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test (e.g. fix(dashboards): remove infinite loop during login). The Validate PR Title check blocks merging otherwise, and the title becomes the squash-merge commit that drives semantic-release — use feat/fix only for user-facing value.
Never mention client/customer names or their data examples anywhere in the PR title, description, or commit messages. Redact to generic terms ("a customer", "an org", "example values") even when a Linear ticket or issue references the customer by name.
Never quote, summarize, or attribute Slack messages or other internal-communication content anywhere in the PR title, description, or commit messages — even when Slack/internal chatter was used as an investigation or evidence source. Cite only that the signal was checked and what it showed, in generic terms (no channel names, no quoted text, no who-said-what).
Always close or reference a ticket — GitHub issue or Linear ticket, either one is enough. Use Closes: #XXXXX / Closes: PROD-XXXX to close it, or Relates: if it shouldn't auto-close. A GitHub issue automatically creates a Linear counterpart (the reverse is not true), so a GitHub issue alone fully satisfies this rule — do not ask for a Linear ticket when a GitHub issue is already referenced. If neither exists, do not fabricate one and do not silently omit it — flag it to the developer and ask. Only open the PR without a ticket once they explicitly confirm there isn't one.
Subticket → parent's GitHub issue is Relates, not Closes. A subticket's PR should not close the parent's tracking issue; add it as related.

Footer Format

PR closing a GitHub issue (its Linear counterpart is created and closed automatically):


Closes: #22801

PR closing a Linear ticket only (no GitHub issue exists):


Closes: PROD-7478

Subticket (closes the Linear subticket; the GitHub issue belongs to the parent, so relate it):


Closes: PROD-7478
Relates: #22801

Checklist Before Opening

The PR title is a valid conventional commit (type(scope): description)
No client/customer name or their data anywhere in the title, body, or commits
No quoted/summarized Slack or internal-communication content anywhere in the title, body, or commits
A Closes:/Relates: line for a ticket (GitHub issue or Linear) is present, OR the developer explicitly confirmed there's no ticket
Subtickets relate (not close) the parent's GitHub issue

Frequently asked questions

What does the Creating Pull Requests AI skill do?

Why use Creating Pull Requests on TypingMind?

Because you install it once and use it with any model. Creating Pull Requests is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Creating Pull Requests in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/lightdash/lightdash/tree/main/.claude/skills/creating-pull-requests. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Creating Pull Requests?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Creating Pull Requests?

As many as you like. As long as a model supports skills, you can use Creating Pull Requests with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Creating Pull Requests AI skill free?

It is published on GitHub by lightdash. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Ci Limits

openclaw

OrganizationPopular

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Openclaw Debugging

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored…

Openclaw Live Updater

openclaw

OrganizationPopular

Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation. Use for fast-forward update…

Openclaw Pr Maintainer

openclaw

OrganizationPopular

Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Creating Pull Requests

Rules

Footer Format

Checklist Before Opening

Frequently asked questions

Related AI Skills

Set up your own AI workspace now