New: 98,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

Submit PR

by FutureTense in FutureTense/keymaster

Procedure for preparing and submitting pull requests in keymaster, enforcing the required PR template (.github/PULLREQUESTTEMPLATE.md), checklist validation, and quality gates.

MITAuto-check passedDevelopment

Install Submit PR

skills CLI
$ npx skills add FutureTense/keymaster --skill submit-pr -a claude-code

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

GitHub CLI
$ gh skill install FutureTense/keymaster submit-pr --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/FutureTense/keymaster.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/submit-pr .claude/skills/submit-pr && 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
submit-pr
GitHub stars
349
Token cost
~830 tokens
SKILL.md length
252 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Procedure for preparing and submitting pull requests in keymaster, enforcing the required PR template (.github/PULLREQUESTTEMPLATE.md), checklist validation, and quality gates.

  • Works in 3 steps: Format, Linting & Type Checking → Frontend Build & Tests (if frontend… → Integration Tests & Coverage
  • Tasks that involve Pull requests
  • SKILL.md covers Pre-PR Quality Gates Checklist, Mandatory Pull Request Template and Template Format Reference
  • Calls yarn, ruff and mypy

What it does

Submit PR is an agent skill from FutureTense/keymaster. Procedure for preparing and submitting pull requests in keymaster, enforcing the required PR template (.github/PULLREQUESTTEMPLATE.md), checklist validation, and quality gates.

Its SKILL.md is about 830 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 Quality gates. It works with GitHub. The repository describes itself as: Home Assistant integration for managing Z-Wave enabled locks. The licence is MIT.

When your agent uses it

  • Tasks that involve Pull requests
  • Tasks that involve Quality gates

Example prompts

  • “/submit-pr”

Workflow steps

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

  1. Format, Linting & Type Checking
  2. Frontend Build & Tests (if frontend modified)
  3. Integration Tests & Coverage

What it can do on your machine

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

    • yarn
    • ruff
    • mypy
    • pytest

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use yarn, 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

Submit PR loads about 830 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 252 words of instructions outside code blocks.

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

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 FutureTense/keymaster at commit d94ffb2, republished under its MIT licence (© FutureTense). 252 words, ~830 tokens.

Download SKILL.mdSave it as .claude/skills/submit-pr/SKILL.md (or your agent's skills folder).
name
submit-pr
description
Procedure for preparing and submitting pull requests in keymaster, enforcing the required PR template (.github/PULL_REQUEST_TEMPLATE.md), checklist validation, and quality gates.

Pull Request Submission Guide for Keymaster

This skill provides step-by-step instructions for preparing, validating, and submitting pull requests to the Keymaster repository.

Pre-PR Quality Gates Checklist

Before creating a PR, ensure all verification steps pass locally:

  1. Format, Linting & Type Checking:

    bash
    # Run full CI lint environment via tox:
tox -e lint

# Or run individual tools:
ruff check --fix .
ruff format .
mypy .
codespell custom_components/keymaster tests

  2. Frontend Build & Tests (if frontend modified):

    bash
    yarn lint
yarn test
yarn build

  3. Integration Tests & Coverage:

    bash
    # Run standard test suite
pytest --cov=custom_components/keymaster --cov-report=term-missing

# Or run via tox:
tox -e py314
    • Ensure all tests pass, overall project coverage remains >= 80% ([tool.coverage.report] fail_under = 80), and all newly modified/added lines have thorough test coverage (see patch-coverage skill).

Mandatory Pull Request Template

Every pull request description MUST follow the repository template located at .github/PULL_REQUEST_TEMPLATE.md.

Required Sections & Rules

  1. # Summary:

    • Provide a concise summary of the change and which issue is fixed or linked.
    • Include relevant motivation and context.

  2. ## Breaking change (Include ONLY if applicable; remove section if not a breaking change):

    • Clearly describe what breaks for existing users, why the change was made, and how users can update their configurations to make it work.

  3. ## Proposed change:

    • Describe the architectural and functional changes to communicate to maintainers why the PR should be accepted.

  4. ## Type of change:

    • Check exactly one (1) box from:
      • - [ ] Dependency upgrade
      • - [ ] Bugfix (non-breaking change which fixes an issue)
      • - [ ] New feature (which adds functionality)
      • - [ ] Breaking change (fix/feature causing existing functionality to break)
      • - [ ] Code quality improvements to existing code or addition of tests
    • Note: If changes require multiple boxes, split the work into separate PRs.

  5. ## Additional information:

    • Link related or closed issues:
      • This PR fixes or closes issue: fixes #<issue_number>
      • This PR is related to issue: #<issue_number>

Template Format Reference

markdown
# Summary
<!-- Summary of changes, motivation, and context -->

## Breaking change
<!-- Only include if breaking change, otherwise omit -->

## Proposed change
<!-- Big picture explanation of the changes -->

## Type of change
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New feature (which adds functionality)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests

## Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:

© FutureTense, 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/submit-pr of FutureTense/keymaster.

Open the folder on GitHubat commit d94ffb2

Compare with similar skills

Submit PR 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.

Submit PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Submit PR this skillFutureTense/keymaster349—~830Automated safety check: PassMIT
Pull Requestnoh-rs/nohrs156—~4.1kAutomated safety check: PassMIT
PR Deep VerificationQwenLM/qwen-code28k—~18kAutomated safety check: PassApache-2.0
GitHub Swarm Code Reviewruvnet/agentic-flow8166 repos~6.5kAutomated safety check: PassNone
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Docs AuthoringTracecatHQ/tracecat3.8k—~3.1kAutomated safety check: NotesAGPL-3.0

Similar skills

  • Pull Request

    noh-rs/nohrs

    Take a change from working tree to a merge-ready pull request, then keep iterating until the CI checks and AI reviewers (CodeRabbit, cubic) all pass.

    156 GitHub stars~4.1k tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • PR Deep Verification

    QwenLM/qwen-code

    Runs a sandboxed, evidence-based check of one qwen-code pull request, proving its main change against the base build and writing a report with a machine-readable verdict.

    28k GitHub stars~18k tokensUpdated today
    DevelopmentAuto-check passed

  • GitHub Swarm Code Review

    ruvnet/agentic-flow

    Reviews GitHub pull requests with a swarm of specialized agents covering security, performance, architecture, style and accessibility, driven by the gh CLI and ruv-swarm.

    816 GitHub starsUsed in 6 repos~6.5k tokens
    DevelopmentAuto-check passed

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

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Docs Authoring

    TracecatHQ/tracecat

    A skill your agent uses when adding or updating documentation pages in an existing docs site.

    3.8k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check: notes

  • MAUI PR Performance Analysis

    dotnet/maui

    Official

    Interprets pinned managed benchmark evidence for a dotnet/maui pull request and writes a narrative for the performance review workflow, without running or publishing anything.

    23k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

More from FutureTense/keymaster

  • Ha Code Quality

    FutureTense/keymaster

    Standards and commands for linting, code formatting, typing validation (Ruff, MyPy, Codespell, ESLint, Pre-commit/Prek, Tox), and adherence to Home Assistant Python 3.14 standards in Keymaster.

    349 GitHub stars~462 tokensUpdated today
    Auto-check passed

  • Ha Integration Testing

    FutureTense/keymaster

    Workflows, conventions, and commands for writing and running async Home Assistant unit and integration tests using pytest, tox, pytest-homeassistant-custom-component, and coverage tools.

    349 GitHub stars~522 tokensUpdated today
    Auto-check passed

  • Ha Lock Provider

    FutureTense/keymaster

    Guide for developing, testing, and maintaining lock platform providers (e.g., zwavejs, zigbee2mqtt, zha, schlage, akuvox) implementing BaseLockProvider in Keymaster.

    349 GitHub stars~829 tokensUpdated today
    Auto-check passed

  • Patch Coverage

    FutureTense/keymaster

    Procedure and guidelines for verifying and maintaining 100% patch test coverage on all modified and added lines across Keymaster PRs and branches.

    349 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Lovelace Strategy

    FutureTense/keymaster

    Workflows for developing, building, bundling, and testing the TypeScript / Lit Lovelace dashboard strategy in lovelacestrategy/.

    349 GitHub stars~345 tokensUpdated today
    Auto-check passed

  • Coordinator Lifecycle

    FutureTense/keymaster

    Architectural patterns and lifecycle instructions for KeymasterCoordinator, KeymasterLockCoordinator, fan-out notification architecture, child entity platforms, and storage migrations.

    349 GitHub stars~857 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Submit PR

What does Submit PR do?

Procedure for preparing and submitting pull requests in keymaster, enforcing the required PR template (.github/PULLREQUESTTEMPLATE.md), checklist validation, and quality gates. Submit PR is an agent skill from FutureTense/keymaster.md), checklist validation, and quality gates.

When should I use Submit PR?

Submit PR fits situations like: tasks that involve Pull requests; tasks that involve Quality gates.

How do I install Submit PR in Claude Code?

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

How do I install Submit PR in Codex?

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

Can I use Submit PR 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 FutureTense/keymaster --skill submit-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/submit-pr, .gemini/skills/submit-pr, .github/skills/submit-pr and .opencode/skills/submit-pr in your project.

What does Submit PR need to run?

Going by SKILL.md and its folder, Submit PR needs the command-line tools its instructions call (yarn, ruff, mypy and pytest).

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

Submit PR 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 Submit PR use?

About 830 tokens (SKILL.md is roughly 3.3k 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 Submit PR?

Skills that share tags, products or a category with Submit PR: Pull Request (noh-rs/nohrs, 156 stars), PR Deep Verification (QwenLM/qwen-code, 28k stars), GitHub Swarm Code Review (ruvnet/agentic-flow, 816 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 Submit PR?

FutureTense (a GitHub user) maintains it in FutureTense/keymaster, which has 349 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.

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