plugins/teams/skills/coderabbit-inheritance-scanner-check/SKILL.md
Use when checking a repository's .coderabbit.yaml (or .coderabbit.yml) to determine whether inheritance: true is set
npx skillsauth add openshift-eng/ai-helpers coderabbit-inheritance-scanner-checkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill checks a single repository's .coderabbit.yaml (or .coderabbit.yml) to determine whether inheritance: true is set.
Use this skill as Step 2 of the /teams:coderabbit-inheritance-scanner command. Call it once per repo found by the search skill. Multiple repos can be checked in a single bash invocation using the batch procedure below.
For a batch of repos stored in a bash array, run the following to classify each one:
# Input: REPOS array of "org/repo" strings
# Output: prints classification and default branch for each repo
for REPO in "${REPOS[@]}"; do
CONTENT=""
CFGFILE=""
for FILENAME in .coderabbit.yaml .coderabbit.yml; do
CONTENT=$(gh api "repos/${REPO}/contents/${FILENAME}" --jq '.content' 2>/dev/null | base64 -d 2>/dev/null)
if [ -n "$CONTENT" ]; then
CFGFILE="$FILENAME"
break
fi
done
# Get default branch for link generation
DEFAULT_BRANCH=$(gh api "repos/${REPO}" --jq '.default_branch' 2>/dev/null)
if [ -z "$CONTENT" ]; then
echo "ERROR|${REPO}|${DEFAULT_BRANCH}|${CFGFILE}"
continue
fi
if echo "$CONTENT" | grep -qE '^\s*inheritance:\s*true'; then
echo "COMPLIANT|${REPO}|${DEFAULT_BRANCH}|${CFGFILE}"
elif echo "$CONTENT" | grep -qE '^\s*inheritance:\s*false'; then
echo "FALSE|${REPO}|${DEFAULT_BRANCH}|${CFGFILE}"
else
echo "MISSING|${REPO}|${DEFAULT_BRANCH}|${CFGFILE}"
fi
sleep 0.3
done
Pipe-separated fields per line:
STATUS|org/repo|default_branch|config_filename
Where STATUS is one of:
COMPLIANT - inheritance: true is setFALSE - inheritance: false is explicitly setMISSING - the inheritance key is absentERROR - could not fetch the filetesting
Snapshot OpenShift payload data (release controller, PR diffs, comments, CI jobs, JUnit results, regression tracking) to a local directory for offline analysis
research
Shared engine for analyzing Jira issue activity and generating status summaries
tools
This skill should be used before any Snowflake command to verify MCP connectivity, guide users through access provisioning, and set the session context. Invoke this skill proactively whenever a command needs Snowflake data access.
development
Analyze a payload snapshot to identify root causes of blocking job failures, score candidate PRs, and produce an HTML report with revert recommendations