coderabbit-data-handling
Defines rules for CodeRabbit data handling, focusing on secret detection and file exclusions for compliance.
Install
mkdir -p .claude/skills/coderabbit-data-handling && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8768" && unzip -o skill.zip -d .claude/skills/coderabbit-data-handling && rm skill.zipInstalls to .claude/skills/coderabbit-data-handling
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Implement CodeRabbit PII handling, data retention, and GDPR/CCPA complianceKey capabilities
- →Exclude sensitive files from AI review using path filters
- →Configure secret detection patterns for pull requests
- →Limit AI review scope to specific source code directories
- →Implement security-focused path instructions for database and auth code
- →Define data retention and privacy compliance patterns
How it works
The skill uses a .coderabbit.yaml configuration file to define path filters and instructions that control which files the AI engine accesses and how it flags security-sensitive patterns during pull request reviews.
Inputs & outputs
When to use coderabbit-data-handling
- →Exclude sensitive files from AI review
- →Configure secret detection in PRs
- →Implement GDPR data retention policies
- →Set up PII redaction rules
About this skill
CodeRabbit Data Handling
Overview
Manage code review data and sensitive patterns with CodeRabbit. Covers secret detection in PRs, sensitive file exclusion from AI review, review comment data retention, and configuring what code context gets sent to the AI engine.
Prerequisites
- CodeRabbit installed on repository
- Understanding of sensitive file patterns
- Repository admin access for configuration
- Secret scanning tools awareness
Instructions
Step 1: Exclude Sensitive Files from Review
# .coderabbit.yaml - Data handling configuration
reviews:
path_filters:
# Never send these to AI review
- "!**/.env*"
- "!**/credentials*"
- "!**/secrets*"
- "!**/*.pem"
- "!**/*.key"
- "!**/*.p12"
- "!**/serviceAccountKey*"
- "!**/terraform.tfstate*"
- "!**/*.tfvars"
# Exclude large generated files
- "!**/package-lock.json"
- "!**/pnpm-lock.yaml"
- "!**/yarn.lock"
- "!**/*.generated.*"
- "!**/dist/**"
- "!**/coverage/**"
Step 2: Secret Detection Instructions
# .coderabbit.yaml - Instruct AI to flag secrets
reviews:
path_instructions:
- path: "**"
instructions: |
CRITICAL: Flag any of these patterns as HIGH SEVERITY:
- Hardcoded API keys, tokens, or passwords
- AWS access keys (AKIA...)
- Private keys or certificates
- Database connection strings with credentials
- JWT secrets or signing keys
- Webhook URLs with tokens in query params
If you find any secrets, add a comment:
"SECURITY: Hardcoded secret detected. Move to environment variable."
- path: "**/*.{yml,yaml}"
instructions: |
Check CI/CD files for:
- Secrets logged in step names or echo statements
- Unpinned GitHub Actions (use SHA, not tags)
- Missing secret masking in outputs
Step 3: Review Data Scope Management
# Control what context CodeRabbit accesses
reviews:
auto_review:
enabled: true
drafts: false # Don't review draft PRs (may contain WIP secrets)
base_branches:
- "main"
- "develop"
ignore_title_keywords:
- "WIP"
- "DO NOT REVIEW"
- "DRAFT"
# Limit file types reviewed
path_filters:
# Only review source code, not data
- "+src/**"
- "+lib/**"
- "+app/**"
- "+tests/**"
- "+.github/**"
- "!**/*.csv"
- "!**/*.json" # Exclude data files
- "!**/fixtures/**" # Exclude test fixtures with sample data
- "!**/seeds/**" # Exclude database seeds
Step 4: Sensitive Code Pattern Detection
# .coderabbit.yaml - Custom pattern detection
reviews:
path_instructions:
- path: "src/db/**"
instructions: |
Review database code for:
- SQL injection vulnerabilities (string concatenation in queries)
- Unparameterized queries
- PII logged in error messages
- Missing data sanitization on inputs
- path: "src/api/**"
instructions: |
Review API endpoints for:
- User input not validated before processing
- Sensitive data in response bodies (passwords, tokens)
- Missing authentication checks
- Overly permissive CORS configuration
- PII in URL parameters (should be POST body instead)
- path: "src/auth/**"
instructions: |
SECURITY-CRITICAL PATH. Review for:
- Token expiry configuration
- Password hashing (must use bcrypt/argon2, never MD5/SHA)
- Session fixation vulnerabilities
- CSRF protection
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Secret in reviewed PR | Not in exclusion list | Add pattern to path_filters |
| Large diff reviewed | Generated code included | Exclude generated file paths |
| Sensitive fixture data | Test data has real PII | Exclude fixtures directory |
| Review on draft PR | drafts setting enabled | Set drafts: false |
Examples
Minimal Secure Configuration
# .coderabbit.yaml - Security-focused setup
reviews:
auto_review:
enabled: true
drafts: false
path_filters:
- "!**/.env*"
- "!**/*.key"
- "!**/*.pem"
- "!**/secrets/**"
path_instructions:
- path: "**"
instructions: "Flag any hardcoded secrets, API keys, or credentials."
Output
- Sensitive files excluded from AI review via path_filters
- Secret detection instructions configured for all code paths
- Review scope limited to source code only (not data files)
- Security-focused path_instructions for database, API, and auth code
Resources
- CodeRabbit Configuration
- CodeRabbit Path Filters
- CodeRabbit Security
Next Steps
For security hardening, see coderabbit-security-basics.
When not to use it
- →Reviewing draft pull requests if drafts are enabled
- →Reviewing large generated files or data fixtures
- →Handling non-source code files like CSV or JSON
Prerequisites
Limitations
- →Secret detection requires manual addition of patterns to path_filters
- →Large diffs may require exclusion of generated file paths
- →Sensitive fixture data must be explicitly excluded
How it compares
Unlike generic review tools, this workflow explicitly integrates PII protection and secret detection directly into the AI review pipeline via repository-level configuration.
Compared to similar skills
coderabbit-data-handling side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| coderabbit-data-handling (this skill) | 0 | 27d | Review | Intermediate |
| software-security | 21 | 6mo | No flags | Intermediate |
| fix-dependabot-alerts | 18 | 6mo | Review | Intermediate |
| backend-security-coder | 24 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
software-security
project-codeguard
A software security skill that integrates with Project CodeGuard to help AI coding agents write secure code and prevent common vulnerabilities. Use this skill when writing, reviewing, or modifying code to ensure secure-by-default practices are followed.
fix-dependabot-alerts
microsoft
Fix Dependabot security alerts by updating vulnerable npm dependencies. Use when the user mentions "dependabot", "security alerts", "vulnerability", "CVE", or wants to update packages with security issues.
backend-security-coder
sickn33
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
equilateral-agents
Equilateral-AI
22 production-ready AI agents with database-driven orchestration for security reviews, code quality analysis, deployment validation, infrastructure checks, and compliance. Auto-activates for security concerns, deployment tasks, code reviews, quality checks, and compliance questions. Includes upgrade paths to enterprise features (GDPR, HIPAA, multi-account AWS, ML-based optimization).
top-100-web-vulnerabilities-reference
davila7
This skill should be used when the user asks to "identify web application vulnerabilities", "explain common security flaws", "understand vulnerability categories", "learn about injection attacks", "review access control weaknesses", "analyze API security issues", "assess security misconfigurations", "understand client-side vulnerabilities", "examine mobile and IoT security flaws", or "reference the OWASP-aligned vulnerability taxonomy". Use this skill to provide comprehensive vulnerability definitions, root causes, impacts, and mitigation strategies across all major web security categories.
differential-review
trailofbits
Performs security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.