Skip to content
TrustedSkillsbeta
Back to all skills

Github Pr Assistant

Checked
sltc-dev·vlatest·backend

Automates GitHub pull request reviews, suggests improvements, and summarizes changes for faster, higher quality code merges.

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 sltc-dev/core-foundry --skill github-pr-assistant -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

sltc-dev

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 sltc-dev/core-foundry at 617d1882f4.

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

Scanned
1 file, 72 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 github-pr-assistant skill helps automate and streamline GitHub pull request workflows. It can analyze pull requests, identify potential issues like merge conflicts or failing tests, and suggest improvements based on best practices. This ultimately aims to reduce the time spent reviewing code and improve overall code quality.

When to use it

  • Code review assistance: Use when you need a quick assessment of a pull request before diving into detailed manual review.
  • Merge conflict resolution: Employ when facing merge conflicts, as the skill can potentially suggest resolutions.
  • Automated feedback: Integrate into your CI/CD pipeline to provide automated feedback on code style and potential issues.
  • Onboarding new developers: Help new team members understand PR best practices by leveraging the assistant's suggestions.

Key capabilities

  • Pull request analysis
  • Merge conflict identification
  • Test failure detection
  • Code improvement suggestions
  • Best practice recommendations

Example prompts

  • "Analyze this pull request: [pull request URL]"
  • "Suggest improvements for this code in the PR: [code snippet]"
  • "What are the potential merge conflicts in this PR?"

Tips & gotchas

The skill requires access to a GitHub repository. Ensure that the AI agent has appropriate permissions (read-only or write) to interact with the specified repository and pull requests.