Agent skill

Running Unit Tests

by PSBrew in PSBrew/MkPFS

Run formatting, linting, and tests; then iteratively fix failures until the branch is green.

GPL-3.0Auto-check passedTesting & QA

Install Running Unit Tests

skills CLI
$ npx skills add PSBrew/MkPFS --skill running-unit-tests -a claude-code

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

GitHub CLI
$ gh skill install PSBrew/MkPFS running-unit-tests --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/PSBrew/MkPFS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/running-unit-tests .claude/skills/running-unit-tests && 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
running-unit-tests
GitHub stars
174
Token cost
~429 tokens
SKILL.md length
194 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
GPL-3.0

At a glance

Run formatting, linting, and tests; then iteratively fix failures until the branch is green.

  • Works in 4 steps: Inspect what changed. git status… → Run the validation flow. → Loop until clean. → …
  • Tasks that involve Linting and formatting
  • SKILL.md covers Workflow and Setup notes
  • Calls uv, git and ruff

What it does

Running Unit Tests is an agent skill from PSBrew/MkPFS. Run formatting, linting, and tests; then iteratively fix failures until the branch is green. Use after implementing a feature or fixing a bug to get the branch ready to push. Triggers: "tests", "run tests", "lint", "format", "CI red", "fix failing tests".

Its SKILL.md is about 430 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 Testing & QA, covering Linting and formatting and Unit testing. It works with pytest and Git. The repository describes itself as: Create and Manage Unsigned PFS (Playstation File System) image files with file compression and checksum support. The licence is GPL-3.0.

When your agent uses it

  • Tasks that involve Linting and formatting
  • Tasks that involve Unit testing

Example prompts

  • “run tests”
  • “format”
  • “CI red”
  • “/running-unit-tests”

Workflow steps

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

  1. Inspect what changed. git status --short, git diff --stat, git diff.
  2. Run the validation flow.
  3. Loop until clean.
  4. Final readiness check. Confirm ./run-tests.sh passes cleanly. Optionally re-run pre-commit.

What it can do on your machine

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

    • uv
    • git
    • ruff

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

  • Network

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

Running Unit Tests loads about 429 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 194 words of instructions outside code blocks.

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

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 PSBrew/MkPFS at commit 1d5df56, republished under its GPL-3.0 licence (© PSBrew). 194 words, ~429 tokens.

Download SKILL.mdSave it as .claude/skills/running-unit-tests/SKILL.md (or your agent's skills folder).
name
running-unit-tests
description
Run formatting, linting, and tests; then iteratively fix failures until the branch is green. Use after implementing a feature or fixing a bug to get the branch ready to push. Triggers: "tests", "run tests", "lint", "format", "CI red", "fix failing tests".
context
fork

Running and Fixing Tests

Run ./run-tests.sh at the end of each feature, bug fix, or refactor to ensure the branch is ready to push. It activates .venv, runs uv sync, installs pre-commit hooks, formats with ruff format, auto-fixes with ruff check --fix, then runs uv run --frozen pytest.

Workflow

  1. Inspect what changed. git status --short, git diff --stat, git diff.
  2. Run the validation flow.
    • Preferred: ./run-tests.sh (full flow above).
    • Tests only: uv run --frozen pytest.
    • Pre-commit explicitly: uv run --frozen pre-commit run --all-files.
  3. Loop until clean.
    • Group failures by root cause.
    • Apply minimal, readable fixes; keep behavior stable unless tests show it's incorrect.
    • Add or update focused tests for each bug fix.
    • Re-run ./run-tests.sh (or uv run --frozen pytest for quicker cycles) after each batch.
  4. Final readiness check. Confirm ./run-tests.sh passes cleanly. Optionally re-run pre-commit. Summarize what was fixed and list any remaining risks before push.

Setup notes

  • First-time setup: if .venv/ doesn't exist, run uv sync once, or run ./run-tests.sh.
  • Different virtualenv: set SKIP_VENV=1 and ensure python3 resolves to the desired environment.
  • Faster loops: uv run --frozen pytest -k <pattern> -q to target tests, then finish with full ./run-tests.sh.

© PSBrew, 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/running-unit-tests of PSBrew/MkPFS.

Open the folder on GitHubat commit 1d5df56

Compare with similar skills

Running Unit Tests 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.

Running Unit Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Running Unit Tests this skillPSBrew/MkPFS174—~429Automated safety check: PassGPL-3.0
Adk Setupgoogle/adk-python22k—~993Automated safety check: NotesApache-2.0
Run Pre Gen ChecksGoogleCloudPlatform/magic-modules974—~492Automated safety check: PassCustom licence
Simple Modern Uvjlevy/simple-modern-uv301—~1.9kAutomated safety check: PassMIT
Gateguardana/guardana129—~776Automated safety check: PassApache-2.0
Python Helpershepherdjerred/monorepo112—~2.3kAutomated safety check: PassGPL-3.0

Similar skills

  • Adk Setup

    google/adk-python

    Official

    Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test…

    22k GitHub stars~993 tokensUpdated today
    DevelopmentAuto-check: notes
  • Run Pre Gen Checks

    GoogleCloudPlatform/magic-modules

    Run fast static checks that don't require generating downstreams, including git submodule verification, gofmt formatting, YAML linting, template validation (version-guard and unused-tmpl), mmv1 core…

    974 GitHub stars~492 tokensUpdated today
    Testing & QAAuto-check passed
  • Simple Modern Uv

    jlevy/simple-modern-uv

    Start, selectively modernize, fully migrate, or update Python projects using simple-modern-uv practices: uv, ruff, BasedPyright, pytest, GitHub Actions CI, and tag-driven PyPI publishing.

    301 GitHub stars~1.9k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Gate

    guardana/guardana

    Run this project's verification — the full local CI mirror (ruff, mypy, import contract, pytest with PostgreSQL, coverage floors, dogfood, generated docs and site, the isolated example suites, the…

    129 GitHub stars~776 tokensUpdated today
    Testing & QAAuto-check passed
  • Python Helper

    shepherdjerred/monorepo

    Current Python development guidance for versions, uv and pip, packaging, typing, asyncio, pytest, Ruff, security, and runtime boundaries.

    112 GitHub stars~2.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Kedro Babysit

    kedro-org/kedro

    Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…

    11k GitHub stars~4k tokensUpdated today
    DevelopmentAuto-check passed

More from PSBrew/MkPFS

  • Build a self-contained HTML report as a companion artifact for audits, verifications, research, or long multi-command investigations.

    174 GitHub stars~1.2k tokensUpdated 4 days ago
    Auto-check passed
  • Compact index of upstream projects and reference sources relevant to PKG/PFS/exFAT research.

    174 GitHub stars~2k tokensUpdated 4 days ago
    Auto-check passed
  • Write commit messages, PR titles/descriptions, and GitHub comments with a user-first style; apply release-drafter-compatible labels; produce release-note-ready PR titles.

    174 GitHub stars~910 tokensUpdated 4 days ago
    Auto-check passed
  • Add a new related project or reference source to the Related Projects index.

    174 GitHub stars~1k tokensUpdated 4 days ago
    Auto-check passed

Works with

Questions about Running Unit Tests

What does Running Unit Tests do?

Run formatting, linting, and tests; then iteratively fix failures until the branch is green. Running Unit Tests is an agent skill from PSBrew/MkPFS. Run formatting, linting, and tests; then iteratively fix failures until the branch is green.

When should I use Running Unit Tests?

Running Unit Tests fits situations like: tasks that involve Linting and formatting; tasks that involve Unit testing.

How do I install Running Unit Tests in Claude Code?

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

How do I install Running Unit Tests in Codex?

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

Can I use Running Unit Tests 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 PSBrew/MkPFS --skill running-unit-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/running-unit-tests, .gemini/skills/running-unit-tests, .github/skills/running-unit-tests and .opencode/skills/running-unit-tests in your project.

What does Running Unit Tests need to run?

Going by SKILL.md and its folder, Running Unit Tests needs the command-line tools its instructions call (uv, git and ruff).

Does Running Unit Tests access the network?

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

Is Running Unit Tests 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 Running Unit Tests use?

Running Unit Tests 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 Running Unit Tests use?

About 429 tokens (SKILL.md is roughly 1.7k 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 Running Unit Tests?

Skills that share tags, products or a category with Running Unit Tests: Adk Setup (google/adk-python, 22k stars), Run Pre Gen Checks (GoogleCloudPlatform/magic-modules, 974 stars), Simple Modern Uv (jlevy/simple-modern-uv, 301 stars) and Gate (guardana/guardana, 129 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Running Unit Tests?

PSBrew (a GitHub organization) maintains it in PSBrew/MkPFS, which has 174 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 3, 2026.

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