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

RustPython Test Failure Investigation

by RustPython in RustPython/RustPython

Investigates a failing RustPython test by comparing it with CPython, then either fixes it or gathers the details for an incompatibility report.

MITAuto-check passedTesting & QA

Install RustPython Test Failure Investigation

skills CLI
$ npx skills add RustPython/RustPython --skill investigate-test-failure -a claude-code

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

GitHub CLI
$ gh skill install RustPython/RustPython investigate-test-failure --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/RustPython/RustPython.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/investigate-test-failure .claude/skills/investigate-test-failure && 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
investigate-test-failure
GitHub stars
22k
Token cost
~467 tokens
SKILL.md length
178 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Investigates a failing RustPython test by comparing it with CPython, then either fixes it or gathers the details for an incompatibility report.

  • Working out why one RustPython test fails
  • SKILL.md covers Arguments and Workflow
  • Calls gh, python3 and git
  • Deciding whether a failing test is a quick fix or a bigger compatibility gap

What it does

You give the skill a failing test identifier. The agent reads the test, studies the failure message and traceback, and checks the related RustPython implementation. It then runs the same test under CPython with `python3 -m unittest` and records what the expected behavior and output are.

A simple cause such as an import problem or a small logic bug gets a fix, followed by formatting, checks, a `git diff` review, a focused subagent review against CPython behavior and a commit. A larger gap, like a missing feature, is written up with the repository's incompatibility issue template: the feature, a minimal reproduction, CPython and RustPython output and a link to the Python documentation. A GitHub issue is created only when you explicitly ask.

When your agent uses it

  • Working out why one RustPython test fails
  • Deciding whether a failing test is a quick fix or a bigger compatibility gap
  • Preparing the details for an incompatibility issue

Example prompts

  • “Investigate why test_inspect.TestGetSourceBase.test_getsource_reload fails and fix it if it is simple.”
  • “Compare this failing test with CPython and tell me whether it is worth fixing now.”
  • “Collect the reproduction and CPython output for the failing test so I can file an incompatibility issue.”

Requirements

  • A RustPython checkout with Cargo
  • `python3` to run the reference test under CPython
  • Pre-approved tools (allowed-tools): Bash(python3:*), Bash(cargo run:*), Bash(gh issue create:*), Read, Grep, Glob, Bash(git add:*), Bash(git commit:*), Bash(cargo fmt:*), Bash(git diff:*), Task

What it can do on your machine

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

    • Bash(python3:*)
    • Bash(cargo run:*)
    • Bash(gh issue create:*)
    • Read
    • Grep
    • Glob
    • Bash(git add:*)
    • Bash(git commit:*)
    • Bash(cargo fmt:*)
    • Bash(git diff:*)

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

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • python3
    • git
    • cargo

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

  • Network

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

RustPython Test Failure Investigation loads about 467 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 178 words of instructions outside code blocks.

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

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 RustPython/RustPython at commit 4b6ad58, republished under its MIT licence (© RustPython). 178 words, ~467 tokens.

Download SKILL.mdSave it as .claude/skills/investigate-test-failure/SKILL.md (or your agent's skills folder).
name
investigate-test-failure
description
Investigate a failing RustPython test, compare with CPython behavior, and decide whether to implement a fix or prepare incompatibility issue details.
allowed-tools
Bash(python3:*), Bash(cargo run:*), Bash(gh issue create:*), Read, Grep, Glob, Bash(git add:*), Bash(git commit:*), Bash(cargo fmt:*), Bash(git diff:*), Task

Investigate Test Failure

Investigate why a specific test is failing and determine whether it can be fixed now or should be reported as an incompatibility issue.

Arguments

  • Failed test identifier (example: test_inspect.TestGetSourceBase.test_getsource_reload)

Workflow

  1. Analyze the failure cause:
  • Read the test code.
  • Analyze failure message and traceback.
  • Check related RustPython implementation code.
  1. Verify behavior in CPython:
  • Run the test with python3 -m unittest.
  • Document expected behavior/output.
  1. Determine fix feasibility:
  • Simple fix (import issues, small logic bugs): implement fix, run formatting and checks, review changes, and commit.
  • Complex fix (major missing feature): gather issue information and report to user.

Pre-commit review process:

  • Run git diff to review local changes.
  • Use a focused subagent review to compare implementation against CPython behavior and check for missed edge cases.
  • Commit only after review passes.
  1. For complex issues, collect issue information using .github/ISSUE_TEMPLATE/report-incompatibility.md:
  • Feature: missing or broken Python feature.
  • Minimal reproduction code.
  • CPython behavior (python3).
  • RustPython behavior (cargo run).
  • Python documentation reference link.

Report the collected information to the user. Create an issue only when explicitly requested.

Example issue command:

shell
gh issue create --template report-incompatibility.md --title "..." --body "..."

© RustPython, 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/investigate-test-failure of RustPython/RustPython.

Open the folder on GitHubat commit 4b6ad58

Compare with similar skills

RustPython Test Failure Investigation 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.

RustPython Test Failure Investigation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
RustPython Test Failure Investigation this skillRustPython/RustPython22k—~467Automated safety check: PassMIT
Dbgtheodo-group/debug-that158—~1.9kAutomated safety check: PassMIT
OpenLogi Change VerificationAprilNEA/OpenLogi23k—~1.4kAutomated safety check: PassApache-2.0
CI Failure Analysisvortex-data/vortex3.2k—~810Automated safety check: PassApache-2.0
Test Specialisttravisjneuman/.claude101—~3.7kAutomated safety check: PassMIT
Browser4 Fix Bugplatonai/Browser41.2k—~1.5kAutomated safety check: PassApache-2.0

Similar skills

  • Dbg

    theodo-group/debug-that

    Debug applications using the dbg CLI debugger. An agent skill from theodo-group/debug-that.

    158 GitHub stars~1.9k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed

  • OpenLogi Change Verification

    AprilNEA/OpenLogi

    Plans the smallest check that could disprove a code change in the OpenLogi project, then escalates through reproduction, focused tests and a final gate before a push.

    23k GitHub stars~1.4k tokensUpdated 3 days ago
    Testing & QAAuto-check passed

  • CI Failure Analysis

    vortex-data/vortex

    Analyze Vortex GitHub Actions CI failures. An agent skill from vortex-data/vortex.

    3.2k GitHub stars~810 tokensUpdated today
    Testing & QAAuto-check passed

  • Test Specialist

    travisjneuman/.claude

    Test-writing patterns for JS/TS, Python, Go, and Rust (unit, integration, E2E, visual regression).

    101 GitHub stars~3.7k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Browser4 Fix Bug

    platonai/Browser4

    Fix bugs in code using a compile-test-fix loop: run the build/tests, read the error, locate the faulty lines, edit, and re-verify until green.

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

  • Failure Oriented Instrumentation

    ArabelaTso/Skills-4-SE

    Selectively instruments code to capture runtime data for debugging failures and bugs.

    253 GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from RustPython/RustPython

  • Apple Container Test Runner

    RustPython/RustPython

    Runs RustPython tests inside a Linux container built with Apple's container CLI, so macOS users can compare Linux results with their local ones.

    22k GitHub stars~467 tokensUpdated today
    Auto-check passed

  • RustPython C-API Expansion

    RustPython/RustPython

    Implements missing CPython C-API functions in RustPython's crates/capi, mapping each header to its module with the pyo3-ffi header split.

    22k GitHub stars~831 tokensUpdated today
    Auto-check passed

  • RustPython Stdlib Upgrade

    RustPython/RustPython

    Upgrades a Python standard library module from CPython into RustPython with update_lib, then triages and marks the tests that still fail.

    22k GitHub stars~876 tokensUpdated today
    Auto-check passed

  • Next Python Stdlib Upgrade Picker

    RustPython/RustPython

    Picks the next CPython standard library module ready for a RustPython upgrade, skipping modules that already have an open upgrade pull request.

    22k GitHub stars~257 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about RustPython Test Failure Investigation

What does RustPython Test Failure Investigation do?

Investigates a failing RustPython test by comparing it with CPython, then either fixes it or gathers the details for an incompatibility report. You give the skill a failing test identifier. The agent reads the test, studies the failure message and traceback, and checks the related RustPython implementation.

When should I use RustPython Test Failure Investigation?

RustPython Test Failure Investigation fits situations like: working out why one RustPython test fails; deciding whether a failing test is a quick fix or a bigger compatibility gap; preparing the details for an incompatibility issue.

How do I install RustPython Test Failure Investigation in Claude Code?

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

How do I install RustPython Test Failure Investigation in Codex?

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

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

What does RustPython Test Failure Investigation need to run?

Going by SKILL.md and its folder, RustPython Test Failure Investigation needs the command-line tools its instructions call (gh, python3, git and cargo). Our summary lists: A RustPython checkout with Cargo; `python3` to run the reference test under CPython. Its frontmatter pre-approves these tools: Bash(python3:*), Bash(cargo run:*), Bash(gh issue create:*), Read, Grep, Glob, Bash(git add:*), Bash(git commit:*), Bash(cargo fmt:*), Bash(git diff:*), Task.

Does RustPython Test Failure Investigation access the network?

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

Is RustPython Test Failure Investigation 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 RustPython Test Failure Investigation use?

RustPython Test Failure Investigation 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 RustPython Test Failure Investigation use?

About 467 tokens (SKILL.md is roughly 1.9k 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 RustPython Test Failure Investigation?

Skills that share tags, products or a category with RustPython Test Failure Investigation: Dbg (theodo-group/debug-that, 158 stars), OpenLogi Change Verification (AprilNEA/OpenLogi, 23k stars), CI Failure Analysis (vortex-data/vortex, 3.2k stars) and Test Specialist (travisjneuman/.claude, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains RustPython Test Failure Investigation?

RustPython (a GitHub organization) maintains it in RustPython/RustPython, which has 22,381 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.

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