Skip to content
TrustedSkillsbeta
Back to all skills
Not found in its repository. We could not find this skill in its repository when we last checked (1999f64, 30 Oct 2026). It is left out of listings and search until a later check finds it again.

Pr Comment Analyzer

Checked
zenobi-us·vlatest·other·MIT

Analyzes PR comments to identify sentiment and key themes, boosting brand understanding & response strategy effectiveness.

Repository

Install on your platform

This skill no longer installs under the name pr-comment-analyzer. zenobi-us/dotfiles no longer contains any SKILL.md.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-30. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

zenobi-us

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 zenobi-us/dotfiles at b8fd7910f5.

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

Commit
b8fd7910f5
Manifest
files/devtools/agent/bundles/developer/skills/git/github-pr-comment-analyzer/SKILL.md
Scanned
4 files, 1,551 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 pr-comment-analyzer skill analyzes pull request comments to extract key information. It can identify action items, assignees, and sentiment expressed in these comments. This allows users to quickly understand the context of a pull request discussion and prioritize tasks based on comment content.

When to use it

  • Summarizing PR discussions: Quickly get an overview of what needs to be done based on feedback in a pull request.
  • Identifying action items: Automatically extract tasks assigned within pull request comments, ensuring nothing falls through the cracks.
  • Gauging sentiment: Understand the overall tone and potential concerns raised during code review.
  • Assignee tracking: Determine who is responsible for addressing specific points in a PR discussion.

Key capabilities

  • Action item extraction
  • Assignee identification
  • Sentiment analysis of comments

Example prompts

  • "Analyze the pull request comments and list all action items."
  • "Who has been assigned to address issues mentioned in these pull request comments?"
  • "What is the overall sentiment expressed in the pull request comments?"

Tips & gotchas

The skill’s effectiveness depends on clear and well-formatted pull request comments. It may struggle with ambiguous or informal language.