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

Preflight

by openfootmanager in openfootmanager/openfootmanager

Verify a pull request with the frontend scripts, default and MCP backend tests and clippy, formatting, architecture checks and review evidence.

GPL-3.0Auto-check passedDevelopment

Install Preflight

skills CLI
$ npx skills add openfootmanager/openfootmanager --skill preflight -a claude-code

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

GitHub CLI
$ gh skill install openfootmanager/openfootmanager preflight --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/openfootmanager/openfootmanager.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/preflight .claude/skills/preflight && 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
preflight
GitHub stars
1.1k
Token cost
~1.3k tokens
SKILL.md length
605 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
GPL-3.0

At a glance

Verify a pull request with the frontend scripts, default and MCP backend tests and clippy, formatting, architecture checks and review evidence.

  • Works in 5 steps: Scope and install → Frontend gates → Backend gates, default and MCP → …
  • Tasks that involve Pull requests
  • SKILL.md covers 1. Scope and install, 2. Frontend gates, 3. Backend gates, default and… and 4. Review evidence, plus 1 more section
  • Calls npm, cargo and git

What it does

Preflight is an agent skill from openfootmanager/openfootmanager. Verify a pull request with the frontend scripts, default and MCP backend tests and clippy, formatting, architecture checks and review evidence. Report results and unrun checks without claiming a local pass guarantees CI.

Its SKILL.md is about 1.3k 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. It works with Model Context Protocol, npm, Tauri and Rust. The repository describes itself as: An open source soccer/football manager game. The licence is GPL-3.0.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/preflight”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash(npm ci), Bash(npm test*), Bash(npm run*), Bash(cargo test*), Bash(cargo clippy*), Bash(cargo fmt*), Bash(git status), Bash(git diff*), Bash(git log*), Bash(git branch*)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Scope and install
  2. Frontend gates
  3. Backend gates, default and MCP
  4. Review evidence
  5. Merge hygiene and collisions

What it can do on your machine

Read from SKILL.md and the folder at commit 90b05fd. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Bash(npm ci)
    • Bash(npm test*)
    • Bash(npm run*)
    • Bash(cargo test*)
    • Bash(cargo clippy*)
    • Bash(cargo fmt*)
    • Bash(git status)

    …and 3 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • cargo
    • git

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

  • Network

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

Preflight loads about 1.3k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 605 words of instructions outside code blocks.

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

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 openfootmanager/openfootmanager at commit 90b05fd, republished under its GPL-3.0 licence (© openfootmanager). 605 words, ~1,323 tokens.

Download SKILL.mdSave it as .claude/skills/preflight/SKILL.md (or your agent's skills folder).
name
preflight
description
Verify a pull request with the frontend scripts, default and MCP backend tests and clippy, formatting, architecture checks and review evidence. Report results and unrun checks without claiming a local pass guarantees CI.
allowed-tools
Read, Grep, Glob, Bash(npm ci), Bash(npm test*), Bash(npm run*), Bash(cargo test*), Bash(cargo clippy*), Bash(cargo fmt*), Bash(git status), Bash(git diff*), Bash(git log*), Bash(git branch*)
when_to_use
Before opening or updating a pull request or asking for review.

Preflight

Read the root Code quality section first. It names the limits and which gates are live. Verify without mutating formatting or weakening tests. Stop on a failure, fix within scope, then resume from that step; disclose unrelated blockers. Never report an unrun check as passing.

1. Scope and install

bash
git branch --show-current
git status --short
git diff --stat upstream/develop...HEAD
npm ci

Work on a branch off current upstream/develop, targeting develop. Check for unrelated files, exported worlds, local settings and formatting churn. npm ci precedes frontend commands in a fresh checkout. Use npm run <script>, never npx: a cached namesake can silently run the wrong tool.

2. Frontend gates

bash
npm run preflight

package.json defines this frontend sequence: format check, lint, knip, build, tests. npm run build already does tsc && vite build; do not repeat a separate type check. For a scoped test while iterating, use npm test -- <path> -t '<scenario>' after installing dependencies; the full suite is still required before the PR. Locale and literal-key coverage tests are part of it. A local pass is evidence for these commands, not a guarantee that every CI job passes.

3. Backend gates, default and MCP

bash
cargo fmt --manifest-path src-tauri/Cargo.toml --all -- --check
cargo test --locked --manifest-path src-tauri/Cargo.toml --workspace
cargo test --locked --manifest-path src-tauri/Cargo.toml --lib --features mcp
cargo clippy --locked --manifest-path src-tauri/Cargo.toml --workspace --all-targets -- -D warnings
cargo clippy --locked --manifest-path src-tauri/Cargo.toml --workspace --all-targets --features mcp -- -D warnings

Default workspace tests include command lib tests. The second test command actually executes MCP lib tests; building the feature alone does not. cargo test --bin may run zero tests. Verify that the expected named tests ran. --locked matches CI; if a dependency edit needs a lockfile update, resolve it deliberately and commit the resulting lockfile alongside the manifest.

The pinned rust-toolchain.toml is authoritative. Do not override it with cargo +<toolchain>. No new #[allow]: use the root constraint/owner suppression policy. Do not raise a threshold to fit code. fmt --check reports changes without writing them.

The workspace run includes src-tauri/tests/architecture.rs and, as the programme lands, its crate-matrix, application-import, engine-input and command-size checks, plus file-size and instruction-sync integration tests. Frontend architecture/file-size tests join npm test in programme PR 8. Until each exists, inspect those rules manually and mark them review-only; do not run a missing target or count a zero-test selection as a pass.

Show full SKILL.md (275 more words)Show less

4. Review evidence

Use ofm-architecture-reviewer for architecture and SOLID, ofm-dedup-reviewer for authoritative homes and reachable reuse, and ofm-test-reviewer for any test change and every bug fix (the last agent is added in programme PR 2). Map each named GWT scenario to one independently reported test; quote observed red/fix-removal failure and the green command. Use a disposable copy for fix removal. Do not claim "would fail" as observed evidence. Identify uncovered routes and exceptions.

i18n-auditor and ui-accessibility-reviewer are mandatory when their surfaces change. Read the heuristic report if text changed:

bash
npm run audit:i18n

It always exits 0; it is advisory and cannot replace locale tests or review. New mechanical quality checks must fail required CI at zero findings; this existing heuristic is not such a gate.

Record a compact evidence table in the PR body:

Check / scenarioCommand / test nameObserved resultLimit or exception

Include the canonical rule owner and layer, reviewer results, and every unrun check. Documentation changes have no runtime red/green claim; verify links, identical instruction blocks and scope.

5. Merge hygiene and collisions

  • Conventional commit, fresh develop base, PR target develop, linked issue where applicable.
  • AI-assisted disclosure box completed per CONTRIBUTING.md.
  • Search every other open PR diff for uses of public items/fields/variants removed or changed here, and for removals of items this branch uses. Agree merge order with the owner on a collision. The second PR stays draft with ⛔ Merge after #<first> as its body's first line. Once the first merges, merge upstream/develop, adapt, rerun gates, then mark ready.
  • Recheck when a merge touches your surfaces. The develop merge queue reruns required checks; local evidence does not replace the queue. Do not alter repository settings.

© openfootmanager, GPL-3.0. 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 .claude/skills/preflight of openfootmanager/openfootmanager.

Open the folder on GitHubat commit 90b05fd

Compare with similar skills

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

Preflight compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Preflight this skillopenfootmanager/openfootmanager1.1k—~1.3kAutomated safety check: PassGPL-3.0
Code Reviewoaslananka/kicad-mcp-pro120—~3.9kAutomated safety check: PassMIT
Agentbro PR Mergeshirenchuang/agentbro203—~648Automated safety check: PassApache-2.0
Rocketmq Rust PR Submittermxsm/rocketmq-rust1.5k—~1.4kAutomated safety check: PassApache-2.0
Resolve PR Reviewshencangsheng/easydb_app590—~2.4kAutomated safety check: PassMIT
Agentbro Releaseshirenchuang/agentbro203—~2.5kAutomated safety check: PassApache-2.0

Similar skills

  • Code Review

    oaslananka/kicad-mcp-pro

    A skill your agent uses for GitHub Copilot pull request and code reviews in oaslananka/kicad-mcp-pro.

    120 GitHub stars~3.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Agentbro PR Merge

    shirenchuang/agentbro

    A skill your agent uses when reviewing, fixing CI for, approving workflows for, or merging AgentBro pull requests into dev/main, especially external contributor PRs where contributor attribution…

    203 GitHub stars~648 tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • Rocketmq Rust PR Submitter

    mxsm/rocketmq-rust

    A skill your agent uses when the user asks to prepare, submit, publish, or optimize a pull request for the rocketmq-rust project, especially when the PR title or commit message must follow the [ISSUE

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

  • Resolve PR Review

    shencangsheng/easydb_app

    Resolve pull request code review comments end-to-end. An agent skill from shencangsheng/easydb_app.

    590 GitHub stars~2.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Agentbro Release

    shirenchuang/agentbro

    A skill your agent uses when releasing AgentBro from this repository: merging dev/main, bumping versions, updating release notes, tagging, pushing, monitoring GitHub Actions, Homebrew cask…

    203 GitHub stars~2.5k tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • Project Pull Request

    swimmwatch/cloakbrowser-mcp

    Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work.

    161 GitHub stars~1k tokensUpdated 6 days ago
    DevelopmentAuto-check passed

More from openfootmanager/openfootmanager

  • Add UI String

    openfootmanager/openfootmanager

    Add or change any text a player can see, in every locale the game ships in.

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

  • Add Domain Field

    openfootmanager/openfootmanager

    Add a field to a domain type so it survives save/load. An agent skill from openfootmanager/openfootmanager.

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

  • Add MCP Tool

    openfootmanager/openfootmanager

    Add a tool to the MCP server that lets AI agents play OpenFoot Manager.

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

  • Add Tauri Command

    openfootmanager/openfootmanager

    Expose new backend behaviour to the frontend over Tauri IPC.

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

  • New UI Surface

    openfootmanager/openfootmanager

    Build a new frontend component, panel, dashboard tab, or screen that matches the Matchday design language, works in light and dark, is keyboard and screen-reader accessible, reuses existing…

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

Works with

Categories

Questions about Preflight

What does Preflight do?

Verify a pull request with the frontend scripts, default and MCP backend tests and clippy, formatting, architecture checks and review evidence. Preflight is an agent skill from openfootmanager/openfootmanager. Verify a pull request with the frontend scripts, default and MCP backend tests and clippy, formatting, architecture checks and review evidence.

When should I use Preflight?

Preflight fits situations like: tasks that involve Pull requests.

How do I install Preflight in Claude Code?

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

How do I install Preflight in Codex?

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

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

What does Preflight need to run?

Going by SKILL.md and its folder, Preflight needs the command-line tools its instructions call (npm, cargo and git). Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash(npm ci), Bash(npm test*), Bash(npm run*), Bash(cargo test*), Bash(cargo clippy*), Bash(cargo fmt*), Bash(git status), Bash(git diff*), Bash(git log*), Bash(git branch*).

Does Preflight access the network?

SKILL.md contains no URLs. Its commands use npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Preflight 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 Preflight use?

Preflight is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Preflight use?

About 1.3k tokens (SKILL.md is roughly 5.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 Preflight?

Skills that share tags, products or a category with Preflight: Code Review (oaslananka/kicad-mcp-pro, 120 stars), Agentbro PR Merge (shirenchuang/agentbro, 203 stars), Rocketmq Rust PR Submitter (mxsm/rocketmq-rust, 1.5k stars) and Resolve PR Review (shencangsheng/easydb_app, 590 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Preflight?

openfootmanager (a GitHub organization) maintains it in openfootmanager/openfootmanager, which has 1,135 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.

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