Skip to content
TrustedSkillsbeta
Back to all skills

Pr Test Analyzer

Checked
troykelly·vlatest·testing

Analyzes pull requests for code quality, style adherence, and potential issues using automated checks and suggestions.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add troykelly/codex-skills --skill pr-test-analyzer -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

troykelly

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned troykelly/codex-skills at d8fb3968e4.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d8fb3968e4
Manifest
skills/pr-test-analyzer/SKILL.md
Scanned
1 file, 20 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The troykelly-pr-test-analyzer skill analyzes pull request test results to provide a summary of failures and potential causes. It can identify failing tests, extract error messages, and suggest possible fixes based on the analysis. This helps developers quickly understand and address issues in their code changes.

When to use it

  • Debugging failed builds: After a CI/CD pipeline fails due to test failures, use this skill to get a concise overview of what went wrong.
  • Reviewing pull requests: During code review, leverage the skill to quickly assess the impact and potential issues introduced by changes.
  • Identifying flaky tests: The skill can help pinpoint recurring test failures that might indicate instability in the codebase.
  • Understanding complex error messages: When faced with cryptic or lengthy error outputs from tests, use this skill for clarification.

Key capabilities

  • Analyzes pull request test results
  • Identifies failing tests
  • Extracts error messages
  • Suggests potential fixes

Example prompts

  • "Analyze the latest PR test results and summarize the failures."
  • "What are the top 3 failing tests in this pull request?"
  • "Explain why test 'LoginTest' failed based on the provided output."

Tips & gotchas

The skill requires access to the pull request test result data, typically through a CI/CD system or testing framework. The accuracy of suggested fixes depends on the quality and clarity of the test results themselves.