What is github.get_pr_to_pass_local_tests?

A pull request test-fixing workflow that runs the local unit tests and investigates failures. Unit tests are small automated checks of individual pieces of code.

Use it to check a current pull request with the local test suite, identify regressions, and post either a passing status or a failure summary.

A change can break existing tests, and finding the failures across a full test run can be tedious. This records a plan, runs the tests, and reports the result on the pull request.

How causify-ai/helpers configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to causify-ai/helpers. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/causify-ai/helpers/master/.claude/skills/github.get_pr_to_pass_local_tests/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/causify-ai/helpers

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/causify-ai/helpers/github.get_pr_to_pass_local_tests/github.svg)](https://agentmods.dev/skills/causify-ai/helpers/github.get_pr_to_pass_local_tests)

Your own site

<a href="https://agentmods.dev/skills/causify-ai/helpers/github.get_pr_to_pass_local_tests"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/github.get_pr_to_pass_local_tests/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/causify-ai/helpers/github.get_pr_to_pass_local_tests"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/github.get_pr_to_pass_local_tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 718 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00010	$0.00718
Opus 5.5	$0.00004	$0.00287
Sonnet 5.5	$0.00002	$0.00144
Haiku 4.5	$0.00001	$0.00072

Measured 16d ago against content hash 47138c19da02, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

github.get_pr_to_pass_local_tests scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 16d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/github.get_pr_to_pass_local_tests/SKILL.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Goal

Run, monitor, and fix the local unit tests for the current PR

Workflow

Create and Update a Plan

Create a file plan-github.get_pr_to_pass_local_tests.md with a plan in the form of a bullet list of actions and maintain it updated, by marking each action
- [.] when something is in progress
- when something is done
- [F] when something failed

Get the PR Number and Branch Name

Get the PR number

> GH_PR_NUM=$(gh pr view --json number -q .number)

Get the branch name

> BRANCH_NAME=$(git branch --show-current)

Run Local Regressions

Run full test suite locally:

> pytest_multi_build.py --target . 2>&1 --timeout -1 | tee tmp.auto_task.pytest_multi_build.log

Wait for the script to terminate

Check Regressions to Complete

Check the output of the local regressions with:

> pytest_failed_multi_build.py 2>&1 | tee tmp.auto_task.pytest_failed_multi_build.log

Report Status on the PR

If local regressions are passing:

> gh pr comment $GH_PR_NUM --body "Local tests passing"

If any failures, document error and post:

> gh pr comment $GH_PR_NUM --body "Local test failures found: [error summary]. Investigating..."

Fix the Failures

If failures were found, run tmp.pytest_failed_multi_build.repro.sh to understand what failed and use /pytest.fix_local_tests to analyze and fix them
- If the fix is simple, just fix it and commit
- If the fix is not clear, stop and ask for the user to help

Never Commit Junk Files

Never run git add -A or git add . to stage a fix: it sweeps in every untracked file sitting in the working tree (logs, tmp.* scratch files, test-run artifacts like .pkl/.json caches, etc.), not just the files you intended to fix
Always stage files explicitly by path, e.g. git add <file1> <file2>
Before committing, run git status --short and review every listed file; drop anything that is not part of the intended fix
If junk files were already committed and pushed, fix it by amending the commit to contain only the intended files and force-pushing (git push --force-with-lease), rather than leaving the junk in history

Read the full file on GitHub · 83 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

16d ago Changed 47138c19da02
1mo ago Changed 13ab3122cb4b
1mo ago First seen · 83 lines · 10 tokens per session scan A 6df3414edeb0

Subscribe to this mod's changes

github.get_pr_to_pass_local_tests is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 718 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-13.

Testing Unit testing

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

migrate-xunit-to-xunit-v3

Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…

dotnet/skills · 149 tokens

helpers: Skill for Claude Code