jentic-api-scorecard: Skill for Claude Code

/review-community — review someone else's PR with the community tone

This skill wraps the built-in /review command with two additions:

1. Authorship guard — refuses to run if the PR author's GitHub login matches the current user's. For self-reviews, use /review directly with its default voice.
2. Tone injection — inlines the diplomatic review-comments style into this turn so the tone applies without flipping the session output style. Activating the style via /config → Output style would replace Claude Code's default software-engineering system prompt; this skill avoids that by overlaying the tone on top of the default.

Tone for this review

The tone, structure, and constraints below are the source of truth for voice and feedback structure. Follow them for every comment drafted in this review.

!cat .claude/output-styles/review-comments.md

Phase 0 — Resolve PR and verify authorship

Run this once and use the values for the rest of the skill. set -e ensures any failed command stops the block; if it stops, surface the error to the user and do not proceed.

set -e

if [ -n "$ARGUMENTS" ]; then
  PR="$ARGUMENTS"
else
  PR=$(gh pr view --json number -q .number)
fi

PR_AUTHOR=$(gh pr view "$PR" --json author -q .author.login)
GH_USER=$(gh api user -q .login)

echo "PR=$PR"
echo "PR_AUTHOR=$PR_AUTHOR"
echo "GH_USER=$GH_USER"

Expected outcomes:

• gh pr view with no argument fails (no PR for current branch) → stop and ask the user for a PR number or URL. Don't guess.
• gh api user fails or returns empty $GH_USER → stop. The authorship guard cannot run without a confirmed login. Tell the user to authenticate (gh auth status) and try again.
• $PR_AUTHOR equals $GH_USER → stop. Tell the user this is their own PR and to use /review directly. Do not proceed.
• $PR_AUTHOR differs from $GH_USER → continue. State who authored the PR before starting the review, so the user has confirmation the guard saw the right author.