RustPython Test Failure Investigation
RustPython/RustPython
Investigates a failing RustPython test by comparing it with CPython, then either fixes it or gathers the details for an incompatibility report.
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.
Install OpenLogi Change Verification
$ npx skills add AprilNEA/OpenLogi --skill verifying-openlogi-changes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AprilNEA/OpenLogi verifying-openlogi-changes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/AprilNEA/OpenLogi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/verifying-openlogi-changes .claude/skills/verifying-openlogi-changes && rm -rf skills-srcUse ~/.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/
Install the "verifying-openlogi-changes" agent skill from https://github.com/AprilNEA/OpenLogi/tree/master/.agents/skills/verifying-openlogi-changes into .claude/skills/verifying-openlogi-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-openlogi-changes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/AprilNEA/OpenLogi/tree/master/.agents/skills/verifying-openlogi-changesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add AprilNEA/OpenLogi --skill verifying-openlogi-changes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AprilNEA/OpenLogi verifying-openlogi-changes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AprilNEA/OpenLogi.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/verifying-openlogi-changes .agents/skills/verifying-openlogi-changes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verifying-openlogi-changes" agent skill from https://github.com/AprilNEA/OpenLogi/tree/master/.agents/skills/verifying-openlogi-changes into .agents/skills/verifying-openlogi-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-openlogi-changes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AprilNEA/OpenLogi --skill verifying-openlogi-changes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AprilNEA/OpenLogi verifying-openlogi-changes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AprilNEA/OpenLogi.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/verifying-openlogi-changes .cursor/skills/verifying-openlogi-changes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verifying-openlogi-changes" agent skill from https://github.com/AprilNEA/OpenLogi/tree/master/.agents/skills/verifying-openlogi-changes into .cursor/skills/verifying-openlogi-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-openlogi-changes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/AprilNEA/OpenLogi.git --path .agents/skills/verifying-openlogi-changes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add AprilNEA/OpenLogi --skill verifying-openlogi-changes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AprilNEA/OpenLogi verifying-openlogi-changes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AprilNEA/OpenLogi.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/verifying-openlogi-changes .gemini/skills/verifying-openlogi-changes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verifying-openlogi-changes" agent skill from https://github.com/AprilNEA/OpenLogi/tree/master/.agents/skills/verifying-openlogi-changes into .gemini/skills/verifying-openlogi-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-openlogi-changes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install AprilNEA/OpenLogi verifying-openlogi-changesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add AprilNEA/OpenLogi --skill verifying-openlogi-changes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AprilNEA/OpenLogi.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/verifying-openlogi-changes .github/skills/verifying-openlogi-changes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verifying-openlogi-changes" agent skill from https://github.com/AprilNEA/OpenLogi/tree/master/.agents/skills/verifying-openlogi-changes into .github/skills/verifying-openlogi-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-openlogi-changes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AprilNEA/OpenLogi --skill verifying-openlogi-changes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AprilNEA/OpenLogi verifying-openlogi-changes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AprilNEA/OpenLogi.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/verifying-openlogi-changes .opencode/skills/verifying-openlogi-changes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verifying-openlogi-changes" agent skill from https://github.com/AprilNEA/OpenLogi/tree/master/.agents/skills/verifying-openlogi-changes into .opencode/skills/verifying-openlogi-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-openlogi-changes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
verifying-openlogi-changes- GitHub stars
- 23k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 694 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
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.
- Works in 4 steps: Inspect git status --short, staged and… → Read the root iteration policy → Classify the diff by what it controls,… → …
- Planning how to verify a bug fix before touching production code
- SKILL.md covers Classify before running checks, Reproduce regressions before…, Iterate, then stabilize and Select the pre-push gate only…, plus 1 more section
- Calls cargo and git
What it does
Before running any check, the agent classifies the diff: prose or skill text alone does not need a Rust build, while Rust source or build and validation inputs such as Cargo.toml do. It inspects git status and the full diff against the intended base branch, reads the project's iteration policy and the scoped rules for each changed area, and for a push also reads the local gate rules.
For a bug fix, it reproduces the regression with the smallest possible reproducer before changing production code, using the test layer's existing barriers rather than sleeps or retries to paper over ordering bugs, and records the violated invariant and reproduction command. While iterating it runs one focused test or package check, such as cargo test for a single package, and only once things stabilize does it run formatting, the relevant test suite and Clippy across changed areas.
When your agent uses it
- Planning how to verify a bug fix before touching production code
- Deciding how much to test after a Rust-bearing change
- Running the local gate before pushing a branch
Example prompts
- “Reproduce the DPI scaling bug before I fix it, and tell me the exact repro command.”
- “I changed Cargo.toml. What level of verification does that need before I push?”
- “Run the local gate for this branch before I open the pull request.”
Requirements
- A checkout of the OpenLogi Rust project with its AGENTS.md and CI rules
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Inspect git status --short, staged and unstaged diffs, and new files.
- Read the root iteration policy
- Classify the diff by what it controls, not only by extension
- State the proof before editing: affected behavior, likely wrong implementation,
What it can do on your machine
Read from SKILL.md and the folder at commit 4863a45. 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:
cargogit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use 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
OpenLogi Change Verification loads about 1.4k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 694 words of instructions outside code blocks.
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 AprilNEA/OpenLogi at commit 4863a45, republished under its Apache-2.0 licence (© AprilNEA). 694 words, ~1,383 tokens.
Download SKILL.mdSave it as
.claude/skills/verifying-openlogi-changes/SKILL.md (or your agent's skills folder).- name
- verifying-openlogi-changes
- description
- Plans regression proofs and runs OpenLogi verification based on the diff, affected packages, host OS, and work stage. Use when planning a bug fix, after repository changes, when reviewing test coverage, or before an authorized commit or push.
Verify OpenLogi Changes
Use the smallest check that can disprove the change, then apply the required final gate.
Classify before running checks
- Inspect
git status --short, staged and unstaged diffs, and new files. For branch work, include all changes against the intended base, not only the last commit. Preserve unrelated work. Check whether Rust-bearing rebases or conflict resolution occurred since the last full gate. - Read the root iteration policy and each changed area's scoped rules. For a push, also read the local gate. This skill applies those policies; it does not make the pre-push gate mandatory for every local edit.
- Classify the diff by what it controls, not only by extension:
- Prose, skill text, or images alone are non-Rust; do not compile Rust for them.
- Rust source or build/validation inputs are Rust-bearing. A
Cargo.toml, lockfile, toolchain, or CI change is not a docs-only change.
- State the proof before editing: affected behavior, likely wrong implementation, and an input or interaction where the expected result differs from that mistake.
Reproduce regressions before fixing them
- For a bug fix, run the smallest reproducer before changing production code. Drive normal actions or the existing injected backend, not corrupt private state. Confirm failure on the reported path, not a compile error or unrelated setup failure.
- Use the test layer's existing barriers, events, or logical time. Do not add sleeps or retries to hide an ordering bug.
- Record the violated invariant, its owner, reproduction command, and observed failure. If reproduction is unavailable, state the missing evidence and what a substitute test proves. Do not claim the original bug is verified fixed.
- After the fix, run the same reproducer and a nearby non-failing case that would catch an overbroad change. Report both before and after results.
Iterate, then stabilize
- While code moves, run one focused test or package check. For Rust, use
cargo test -p <package> <test-filter>orcargo check -p <package>. Inspect the test count; a filter that matches zero tests is not evidence. - Once stable, run formatting, relevant tests, and Clippy for each changed Rust package as specified in the root policy. Check affected consumers for shared API changes. Do not run full-workspace checks after every edit.
- For non-Rust changes, check the actual files: spelling, whitespace, links, manifests, or executable behavior. Select shell/Nix/packaging checks from the CI map, not Rust by habit.
Show full SKILL.md (311 more words)Show less
Select the pre-push gate only when pushing
Use the local gate's non-Rust checks or Rust-bearing tier selection.
For Rust-bearing work, apply the local gate's full-tier triggers first. Do not select the affected-package tier merely because few files changed.
Otherwise derive the affected set from the final dependency graph:
sh cargo tree --workspace --target all --invert <changed-package>Repeat for every changed package. Take the union of workspace packages, including transitive consumers. Run the local gate's affected-package tier for that entire set, not just the edited crate directories.
Use the exact commands and compiler flags in the local gate. Keep Git hooks enabled. After a failure, fix the cause with a focused check, then rerun the applicable tier on the final tree. Do not push a known-red tree.
Add checks for the affected boundary
Consult the CI job map for exact commands:
cargo xtask ci --list lists jobs; cargo xtask ci --dry-run prints planned
commands but does not verify them. Run required named jobs rather than assuming
the host gate reproduces all CI.
| Changed boundary | Additional evidence |
|---|---|
| IPC or serialized wire types | IPC rules, version discipline, fixed-byte wire_format tests; roundtrips alone are insufficient |
Platform cfg code | Cross-platform rules, target checks or the required manual audit; host-green is not cross-platform-green |
| UI or localization | UI workflow, i18n rules, rendered/interaction evidence and catalog checks |
| Fixtures | Fixture workflow, strict offline verification and independent semantic review |
| Dependencies, portable crates, MSRV, docs, packaging | The corresponding extra jobs in the CI map, including wasm/rustdoc when applicable |
Report each command's decisive result, the tested host, and the scope it proves. List failed, skipped, and unavailable checks separately. State real-hardware verification explicitly. Do not count a skip, dry run, or manual audit as an executed test. Do not commit, push, create a PR, rerun remote workflows, or release merely because this skill was loaded; follow the task's authorization.
© AprilNEA, Apache-2.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 .agents/skills/verifying-openlogi-changes of AprilNEA/OpenLogi.
Open the folder on GitHubat commit 4863a45
Compare with similar skills
OpenLogi Change Verification 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| OpenLogi Change Verification this skillAprilNEA/OpenLogi | 23k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| RustPython Test Failure InvestigationRustPython/RustPython | 22k | — | ~467 | Automated safety check: Pass | MIT | |
| Activitypub TestingMicrock/ordinary-claude-skills | 403 | — | ~712 | Automated safety check: Pass | Custom licence | |
| Dbgtheodo-group/debug-that | 158 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Debuggnomeria/usbtree | 690 | — | ~715 | Automated safety check: Pass | MIT | |
| Pester Failure AnalysisPowerShell/PowerShell | 56k | — | ~5.1k | Automated safety check: Pass | MIT |
Similar skills
Activitypub Testing
Microck/ordinary-claude-skills
Testing patterns for PHPUnit and Playwright E2E tests. An agent skill from Microck/ordinary-claude-skills.
Dbg
theodo-group/debug-that
Debug applications using the dbg CLI debugger. An agent skill from theodo-group/debug-that.
Debug
gnomeria/usbtree
Systematic root-cause debugging — reproduce, isolate, fix at the source, prove the fix.
Pester Failure Analysis
PowerShell/PowerShell
Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.
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.
More from AprilNEA/OpenLogi
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
OpenLogi Device Fixture Contribution
AprilNEA/OpenLogi
Guides recording, privacy review and offline verification of OpenLogi device fixtures with the fixture contribute and verify commands, without treating replay as proof of hardware behavior.
GPUI Kit Desktop App Guide
AprilNEA/OpenLogi
Guides building Rust desktop apps with the gpui-kit crate, covering component selection, state ownership, theming and overlays, plus normative GPUI coding rules.
Testing OpenLogi UI
AprilNEA/OpenLogi
Verifies OpenLogi's native GPUI interface with focused tests, the component gallery and a mock agent, choosing the evidence that fits each change.
GPUI Kit Design Guides
AprilNEA/OpenLogi
A required reference to read in full before designing, changing or reviewing any screen in a GPUI Kit desktop application.
OpenLogi Device Diagnosis
AprilNEA/OpenLogi
Finds the first failing layer when an OpenLogi Logitech device is missing or misbehaving across enumeration, open, probe, IPC and UI.
Related
Works with
Categories
Questions about OpenLogi Change Verification
What does OpenLogi Change Verification do?
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. toml do. It inspects git status and the full diff against the intended base branch, reads the project's iteration policy and the scoped rules for each changed area, and for a push also reads the local gate rules.
When should I use OpenLogi Change Verification?
OpenLogi Change Verification fits situations like: planning how to verify a bug fix before touching production code; deciding how much to test after a Rust-bearing change; running the local gate before pushing a branch.
How do I install OpenLogi Change Verification in Claude Code?
Run `npx skills add AprilNEA/OpenLogi --skill verifying-openlogi-changes -a claude-code`. Or copy the skill folder (.agents/skills/verifying-openlogi-changes in AprilNEA/OpenLogi) into .claude/skills/verifying-openlogi-changes in your project. Claude Code loads it when a task matches its description.
How do I install OpenLogi Change Verification in Codex?
Run `npx skills add AprilNEA/OpenLogi --skill verifying-openlogi-changes -a codex`. Or copy the skill folder (.agents/skills/verifying-openlogi-changes in AprilNEA/OpenLogi) into .agents/skills/verifying-openlogi-changes in your project. Codex loads it when a task matches its description.
Can I use OpenLogi Change Verification 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 AprilNEA/OpenLogi --skill verifying-openlogi-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verifying-openlogi-changes, .gemini/skills/verifying-openlogi-changes, .github/skills/verifying-openlogi-changes and .opencode/skills/verifying-openlogi-changes in your project.
What does OpenLogi Change Verification need to run?
Going by SKILL.md and its folder, OpenLogi Change Verification needs the command-line tools its instructions call (cargo and git). Our summary lists: A checkout of the OpenLogi Rust project with its AGENTS.md and CI rules.
Does OpenLogi Change Verification access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is OpenLogi Change Verification 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 OpenLogi Change Verification use?
OpenLogi Change Verification is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does OpenLogi Change Verification use?
About 1.4k tokens (SKILL.md is roughly 5.5k 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 OpenLogi Change Verification?
Skills that share tags, products or a category with OpenLogi Change Verification: RustPython Test Failure Investigation (RustPython/RustPython, 22k stars), Activitypub Testing (Microck/ordinary-claude-skills, 403 stars), Dbg (theodo-group/debug-that, 158 stars) and Debug (gnomeria/usbtree, 690 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains OpenLogi Change Verification?
AprilNEA (a GitHub user) maintains it in AprilNEA/OpenLogi, which has 23,109 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 3, 2026.
Source: AprilNEA/OpenLogi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.