agentmods.dev

pytest.fix_ci_tests

pytest.fix_ci_tests is a skill for Claude Code from gpsaggese/helpers. It costs 10 tokens per session (551 once invoked), scanned A, original, Apache-2.0.

A test-failure investigation tool for GitHub CI, the automated service that runs a project's checks. It reads CI logs and reproduction scripts, checks whether failures happen locally, and helps diagnose and fix them.

In plain words
What is it for?
Use it to investigate failing GitHub CI tests, reproduce them locally, examine container builds, and apply fixes to the failing tests.
Why use it?
It separates problems caused by the code from differences between CI and a developer's machine, such as environment variables, secrets, containers, or flaky tests.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths.

not rated 158repo +1 today A scan 10 tokens original Apache-2.0

Good fit Use it to investigate failing GitHub CI tests, reproduce them locally, examine container builds, and apply fixes to the failing tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gpsaggese/helpers/pytest.fix_ci_tests
View source ↗ gpsaggese/helpers
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add gpsaggese/helpers --skill pytest.fix_ci_tests
Clone the repo
git clone --depth 1 https://github.com/gpsaggese/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.

agentmods badge for pytest.fix_ci_tests

README.md
[![agentmods](https://agentmods.dev/badge/skills/gpsaggese/helpers/pytest.fix_ci_tests/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/pytest.fix_ci_tests)
Your own site
<a href="https://agentmods.dev/skills/gpsaggese/helpers/pytest.fix_ci_tests"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/pytest.fix_ci_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.

agentmods 80×15 button for pytest.fix_ci_tests

Your own site · 80×15
<a href="https://agentmods.dev/skills/gpsaggese/helpers/pytest.fix_ci_tests"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/pytest.fix_ci_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 551 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00551
Opus 5.5 $0.00004 $0.00220
Sonnet 5.5 $0.00002 $0.00110
Haiku 4.5 $0.00001 $0.00055

Measured yesterday against content hash 0bca7e5ccf12, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pytest.fix_ci_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 yesterday.

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/pytest.fix_ci_tests/SKILL.md · 62 lines

What it actually says

Goal

  • Given a run of the GitHub CI, analyze the failures and fix the failing tests

Workflow

  • Read .claude/skills/pytest.rules.md

Parse Logs From CI

  • Parse the output of invoke gh_workflow_list, which lists the failing tests

  • The CI log of the failing tests is in a file <CI_LOG>, e.g.:

    # Log is in 'tmp.failure.check_if_the_linter_was_run.gp_scratch_19.txt'

  • The list of failing tests <FAILING_TESTS> is in a file <REPRO_SCRIPT>, e.g.:

    ... # To run the tests:
... > ./tmp.pytest_repro.fast_tests.sh

Check Whether the Failure Reproduces Locally

  • Parse <CI_LOG>
  • Run <REPRO_SCRIPT> locally to check whether <FAILING_TESTS> fail there too
    • For tests that run Docker or Apple containers, run them with each container build, per ## Analyze the Effect of Container Builds in .claude/skills/pytest.rules.md
  • Note any CI vs. local difference: env vars, secrets, container build, or flakiness. /pytest.fix_local_tests cannot see this CI-specific context, so capture it here

Diagnose and Fix

  • Run /pytest.fix_local_tests with <REPRO_SCRIPT> as <FAILURE_INFO> to diagnose the root cause and fix the failing tests
    • If a failure reproduces only on CI, diagnose the CI-specific cause directly (env, secrets, container build, flakiness) and fix it
  • In plan-pytest.fix_ci_tests.md in the current dir, report a table of which tests pass on CI and locally, and why they fail on CI and locally
  • Verify the fixes per # Verification of the Fix in .claude/skills/pytest.rules.md

Ask the User to Commit

  • Ask the user to review and commit the changes
  • Wait for CI to pick up the changes and run the tests, then repeat the workflow

Verification

  • plan-pytest.fix_ci_tests.md lists a fix for every failing test
  • Every fix follows # Verification of the Fix in .claude/skills/pytest.rules.md
  • The failing tests pass on both CI and locally after the fix
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.

  1. yesterday First seen · 62 lines · 10 tokens per session scan A 0bca7e5ccf12

Subscribe to this mod's changes

pytest.fix_ci_tests is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 551 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-11-06.

DebuggingTestingUnit testing
Related

pytest.fix_ci_tests compared with skills from other repositories

pytest.fix_ci_tests next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
pytest.fix_ci_testsgpsaggese/helpersSkill158todayApache-2.0A10Claude Code
testinggarrytan/gbrainSkill32ktodayMITA63Claude Code
verifyYeachan-Heo/oh-my-claudecodeSkill41ktodayMITA12Claude Code
detect-static-dependenciesdotnet/skillsSkill5.8ktodayMITA135Claude Code
testing-blocksadobe/skillsSkill319todayApache-2.0A61Claude Code
dart-downstream-fixdartsim/dartSkill1.2ktodayBSD-2-ClauseA25Claude Code
experiment-iterative-coderEvoScientist/EvoSkillsSkill48610d agoApache-2.0A145Claude Code