mcp-for-splunk: Command for Claude Code

.cursor/commands/check-pr-feedback.md

check-pr-feedback is a command for Claude Code, Cursor from deslicer/mcp-for-splunk. It costs 13 tokens per session (695 once invoked), scanned A, original, Apache-2.0.

A pull-request checking command for GitHub, where developers review proposed code changes before merging them. It looks for review comments and failed automated checks, then addresses the issues it finds.

In plain words
What is it for?
Use it on a pull request to find code-review comments, inspect workflow results for its latest commit, and fix the reported problems.
Why use it?
It removes the need to inspect review discussions and build-test results in several places. It helps catch requested changes and failed checks before the pull request is merged.

Command for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code command (commands/*.md).

This is deslicer/mcp-for-splunk's own configuration. It tells Claude Code and Cursor how to work on mcp-for-splunk itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-for-splunk configures →

Reuse

Borrowing it

Nothing to install: this file belongs to deslicer/mcp-for-splunk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/deslicer/mcp-for-splunk/main/.cursor/commands/check-pr-feedback.md
Clone the repo
git clone --depth 1 https://github.com/deslicer/mcp-for-splunk

Made for: Claude Code, Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for check-pr-feedback

README.md
[![agentmods](https://agentmods.dev/badge/commands/deslicer/mcp-for-splunk/check-pr-feedback.svg)](https://agentmods.dev/commands/deslicer/mcp-for-splunk/check-pr-feedback)
Your own site
<a href="https://agentmods.dev/commands/deslicer/mcp-for-splunk/check-pr-feedback"><img src="https://agentmods.dev/badge/commands/deslicer/mcp-for-splunk/check-pr-feedback.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 695 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.00695
Opus 5 $0.00006 $0.00347
Sonnet 5 $0.00003 $0.00139
Haiku 4.5 $0.00001 $0.00069

Measured 6d ago against content hash 5178f609cb80, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

check-pr-feedback scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/commands/check-pr-feedback.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Check PR Feedback and Fix Issues

You are tasked with checking for code review comments and CI workflow failures on a Pull Request, then resolving any issues found.

Steps to Follow

1. Get PR Information

First, identify the current PR number and repository. Use the GitHub CLI or API:

# Get current branch
git branch --show-current

# List open PRs for this branch
gh pr list --head $(git branch --show-current) --json number,title,url

2. Check for PR Review Comments

Fetch any code review comments added since PR creation:

# Get PR comments (replace PR_NUMBER)
gh api repos/OWNER/REPO/pulls/PR_NUMBER/comments --jq '.[] | {user: .user.login, body: .body, path: .path, line: .line}'

# Get PR review comments
gh api repos/OWNER/REPO/pulls/PR_NUMBER/reviews --jq '.[] | {user: .user.login, state: .state, body: .body}'

3. Check Workflow Status

Check all workflow runs for the latest commit:

# Get latest commit SHA
LATEST_SHA=$(gh api repos/OWNER/REPO/pulls/PR_NUMBER/commits --jq '.[-1].sha')

# Check workflow runs
gh api "repos/OWNER/REPO/actions/runs?head_sha=$LATEST_SHA" --jq '.workflow_runs[] | {name: .name, status: .status, conclusion: .conclusion, id: .id}'

4. Get Failed Job Details

For any failed workflows, get the specific job and step that failed:

# Get jobs for a failed run (replace RUN_ID)
gh api repos/OWNER/REPO/actions/runs/RUN_ID/jobs --jq '.jobs[] | select(.conclusion == "failure") | {name: .name, steps: [.steps[] | select(.conclusion == "failure") | .name]}'

5. Fix Issues

Based on the feedback:

  • Code review comments: Address each comment by making the suggested changes
  • Workflow failures:
    • Run tests locally first: uv run pytest -v
    • Run linting: uv run ruff check src/ tests/
    • Run type checking: uv run mypy src/
    • Fix any issues found

6. Commit and Push

After fixing issues:

git add -A
git commit -m "fix: address PR feedback

- [Describe changes made]"
git push

Read the full file on GitHub · 93 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 93 lines · 13 tokens per session scan A 5178f609cb80

Subscribe to this mod's changes

check-pr-feedback is a command published in the GitHub repository deslicer/mcp-for-splunk (27 stars, last pushed 3d ago), licensed Apache-2.0. It adds 13 tokens to every session and 695 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.