review-code
/review-code
Review recent code changes for security issues, PII leaks, and bugs against CodingStyle.md. Triggers on "/review-code" or when called by commit skill.
- Author
- thefrederiksen ↗
- Repository
- devthrottle ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Review recent code changes for security issues, PII leaks, and bugs against CodingStyle.md. Triggers on "/review-code" or when called by commit skill.
Original author description
Review recent code changes for security issues, PII leaks, and bugs against CodingStyle.md. Triggers on "/review-code" or when called by commit skill.
How it works
- Triggers
- Workflow
- Common Issues from CodingStyle.md
- WPF-Specific Issues
- Notes
SKILL.md preview
---
name: review-code
description: Review recent code changes for security issues, PII leaks, and bugs against CodingStyle.md. Triggers on "/review-code" or when called by commit skill.
---
# Code Review Skill
Review changed files against docs/CodingStyle.md and check for PII/personal information leaks.
This is a **public repository**. Every commit is visible to the world. The PII check is mandatory.
## Triggers
Invoke with /review-code or when called by commit skill.
## Workflow
STEP 1: Get files to review
Use Bash tool to run: git diff --cached --name-only
Then run: git diff --name-only
Also run: git status to find untracked files.
Collect ALL files from the output, not just .cs files. PII can appear in ANY file type:
.cs, .xaml, .xaml.cs, .json, .md, .txt, .ps1, .bat, .sh, .config, .yaml, .yml, .xml, .csproj, etc.
STEP 2: Read the standards (MANDATORY)
Use the Read tool to read: docs/CodingStyle.md
Do NOT skip this. Do NOT rely on memory. Actually READ this file.
STEP 3: PII and Personal Information Scan (MANDATORY)
This is a PUBLIC REPOSITORY. Any personal information committed here is exposed to the entire internet.
For EVERY changed or untracked file, scan for ALL of the following:
BLOCKING PII (must NEVER be committed):
- Real names of people (developers, employees, users, customers)
- Email addresses (personal or corporate)
- Usernames, account names, Windows user profile names (e.g., "jsmith", "jdoe")
- File paths containing usernames (e.g., C:\Users\jsmith\..., /home/jdoe/...)
- Company names, organization names, internal project codenames
- IP addresses (internal or external, not localhost/127.0.0.1/::1)
- Phone numbers
- Physical addresses, office locations
- API keys, tokens, secrets, passwords (even if expired or fake-looking)
- Internal URLs (intranet, VPN, internal tools, Jira, Confluence)
- Employee IDs, badge numbers
- Machine names, server hostnames (not generic like "localhost")
- Database connection strings with server names
- Git remote URLs containing usernames or internal domains
- Screenshots or images that may contain PII (flag for manual review)
- Session IDs, auth tokens, or cookies from real sessions
- License keys or registration codes
IMPORTANT PATH PATTERNS to flag:
- C:\Users\[anyname]\... -> BLOCKING (exposes Windows username)
- /home/[anyname]/... -> BLOCKING (exposes Linux username)
- /Users/[anyname]/... -> BLOCKING (exposes macOS username)
- \\[servername]\... -> BLOCKING (exposes internal server name)
EXCEPTIONS (NOT PII - do not flag these):
- Generic placeholder paths in code comments explaining patterns (e.g., "E.g., C:\Users\username\...")
- Paths using environment variables (e.g., %USERPROFILE%, $HOME, ~/)
- Paths using AppContext.BaseDirectory, Path.GetTempPath(), Environment.GetFolderPath()
- "localhost", "127.0.0.1", "::1", "0.0.0.0"
- Example/placeholder values clearly marked as such (e.g., "user@example.com")
- Open-source project names and maintainer names from public packages
- Anthropic/Claude branding (this is a Claude Code tool - that's expected)
STEP 3.5: CenCon Documentation Check
Check if docs/cencon/architecture_manifest.yaml exists using the Glob tool.
If docs/cencon/architecture_manifest.yaml does NOT exist:
- Set CENCON_STATUS = SKIPPED
- Add SUGGESTION: "Consider adding CenCon documentation (docs/cencon/)"
- Continue to STEP 3.6
If docs/cencon/architecture_manifest.yaml EXISTS:
1. Read the manifest using the Read tool
2. Extract the last_updated field (format: YYYY-MM-DD)
3. Use Bash to find the most recently modified .cs file in src/:
git log -1 --format="%ai" -- "src/**/*.cs"
4. Documentation is STALE if:
- Any .cs file was modified MORE RECENTLY than the manifest's last_updated date
- OR manifest last_updated is more than 30 days old
5. If STALE:
- Add BLOCKING issue: "CenCon architecture_manifest.yaml is outdated"
- Include: "Last manifest update: [date], Most recent code change: [date]"
- Set CENCON_STATUS = FAIL
6. If CURRENT:
- Set CENCON_STATUS = PASS
STEP 3.6: Security Profile Drift Check
Check if docs/cencon/security_profile.yaml exists using the Glob tool.
If docs/cencon/security_profile.yaml does NOT exist:
- Set SECURITY_DRIFT = SKIPPED
- Continue to STEP 4
If docs/cencon/security_profile.yaml EXISTS:
1. Read the profile using the Read tool
2. Extract the last_verified field (format: YYYY-MM-DD)
3. Calculate days since verification (use today's date)
4. Extract drift.threshold_days (default: 30)
5. If days since verification > threshold_days:
- Add BLOCKING issue: "Security profile drift detected"
- Include: "Last verified: [date], Days since: [N], Threshold: [threshold_days]"
- Set SECURITY_DRIFT = FAIL
6. If within threshold:
- Set SECURITY_DRIFT = PASS
STEP 3.7: Documentation Coverage
Check if public documentation needs updating based on the changes being reviewed.
1. Read docs/public/index.json using the Read tool to get the current documentation manifest
2. Examine the changed files from STEP 1 to classify the change type:
IF the changes include NEW tools (new cc-* tool directories, new CLI executables):
- Check if docs/public/tools/overview.md was updated to include the new tool
- Check if docs/public/index.json references any new dedicated tool pages (if applicable)
- If the new tool is NOT documented:
- Add BLOCKING issue: "New tool [tool-name] added without documentation update"
- Include: "Run /update-docs to generate documentation for the new tool"
- Set DOCS_COVERAGE = FAIL
IF the changes include NEW features or NEW commands (new skills in .claude/skills/, new CLI subcommands, new major functionality):
- Check if corresponding docs/public/ pages exist or were updated
- If NOT documented:
- Add BLOCKING issue: "New feature [feature-name] added without documentation"
- Include: "Run /update-docs before committing"
- Set DOCS_COVERAGE = FAIL
IF the changes are BUG FIXES or REFACTORS:
- Check if the fix changes user-visible behavior (command syntax, output format, default values)
- If behavior changed but docs not updated:
- Add WARNING: "Bug fix changes user-visible behavior but docs not updated"
- Set DOCS_COVERAGE = WARN
- If internal-only change:
- Set DOCS_COVERAGE = PASS
IF docs/public/ files were modified:
- Verify docs/public/index.json is still valid:
- Every "file" path in index.json must point to an actual file in docs/public/
- No orphaned pages (files in docs/public/ without index.json entries, except index.json itself)
- If invalid references found:
- Add BLOCKING issue: "docs/public/index.json has broken file references"
- Set DOCS_COVERAGE = FAIL
IF none of the above conditions apply (no tool/feature/behavior changes):
- Set DOCS_COVERAGE = SKIPPED
STEP 4: Code style review
For each .cs, .xaml, and .xaml.cs file from Step 1:
- Use the Read tool to read the full file
- Compare against the rules from docs/CodingStyle.md
- Record issues with FULL PATH and line number
Issue severities:
- BLOCKING: Must fix. Causes review to FAIL.
- WARNING: Should fix. Review still PASSES.
- SUGGESTION: Nice to have. Review still PASSES.
STEP 5: Present findings
Use this exact format (plain text, no markdown tables):
Code Review Report
Files Reviewed: [count]
Standards Applied: CodingStyle.md, PII Scan
Result: PASS or FAIL
PII/PERSONAL INFORMATION Issues (BLOCKING - must fix before commit):
[full path]:[line]
PII Type: [what kind of PII was found]
Content: [the offending text, redacted if necessary]
Fix: [how to fix it - use environment variables, generics, or remove]
BLOCKING Issues (must fix before commit):
[full path]:[line]
Issue: [what is wrong]
Fix: [how to fix it]
WARNING Issues (should fix):
[full path]:[line]
Issue: [what is wrong]
SUGGESTIONS:
[full path]:[line]
Issue: [what could be improved]
CRITICAL: Use FULL file paths like C:\repos\cc-director\src\CcDirector.Core\Session.cs:45
Never use just the filename.
If NO PII is found, include this line in the report:
PII Scan: CLEAN - No personal information detected in changed files.
STEP 6: Return structured status
At the very end, include these lines exactly:
REVIEW_STATUS: PASS or FAIL
BLOCKING_COUNT: [number]
WARNING_COUNT: [number]
SUGGESTION_COUNT: [number]
PII_COUNT: [number]
CENCON_STATUS: PASS, FAIL, or SKIPPED
SECURITY_DRIFT: PASS, FAIL, or SKIPPED
DOCS_COVERAGE: PASS, FAIL, WARN, or SKIPPED
FAIL if any of:
- BLOCKING issues exist
- PII issues exist
- CENCON_STATUS is FAIL
- SECURITY_DRIFT is FAIL
- DOCS_COVERAGE is FAIL
PASS if none of the above conditions are true. SKIPPED and WARN status do NOT cause FAIL.
## Common Issues from CodingStyle.md
BLOCKING:
- Null-forgiving operator (!) to suppress warnings
- Using .Result or .Wait() on async
- Swallowing exceptions silently
- Fallback programming patterns
- Hard-coded credentials
- Missing FileLog.Write in public methods
- UI blocking operations (synchronous I/O on UI thread)
- Using git add . or git add -A
WARNING:
- Private fields without underscore prefix
- Methods over 50 lines
- async void methods (except event handlers)
- IDisposable without disposal
- Missing parameter validation at method start
- Dispatcher.Invoke instead of Dispatcher.BeginInvoke
## WPF-Specific Issues
BLOCKING:
- ObservableCollection modified from background thread without Dispatcher
- File I/O or network calls on UI thread without Task.Run
WARNING:
- Missing INotifyPropertyChanged on ViewModels
- UI elements without DataContext binding
## Notes
Focus on changed code, not legacy issues.
Be specific with line numbers.
The commit skill depends on the REVIEW_STATUS line.
PII scan applies to ALL file types, not just code files.
---
**Skill Version:** 4.0
**Last Updated:** 2026-03-01
**Adapted from:** internal review-code skill
**CenCon Integration:** Added STEP 3.5 (Documentation Check) and STEP 3.6 (Security Drift Check)
**Docs Enforcement:** Added STEP 3.7 (Documentation Coverage) - blocks on new tools/features without docs
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · thefrederiksen/devthrottle | 98 | MIT |
| doodledood/manifest-dev | 100 | MIT |
| serpro69/claude-toolbox | 100 | Apache-2.0 |
| serpro69/claude-toolbox | 100 | Apache-2.0 |
| jelvodev/yaap | 100 | MIT |
| globalmindsolution/gms-marketplace | 100 | MIT |
| tojim00d/Orbit-skills | 100 | MIT |
| yaohuangguan/agent-playbook | 100 | MIT |
| paultyng/skill-issue | 100 | MIT |
Database snapshot: 13.11.2026 · package version 8d168321d7c4 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100code-review
Review C code changes for correctness, safety, and style. Use this when you want to review C code changes or PRs. - 100review
Comprehensive code review of recent changes in the iam-policy-validator project. Use when the user wants a code review, quality check, or audit of recent changes. Triggers on "/review", "review my changes", "code review", or "check code quality". - 100review-pr
Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "the `review-pr` skill". - 100code-review
Reviews code changes for bugs, style issues, security vulnerabilities, and best practices. Use when reviewing PRs, checking code quality, or validating implementations. - 100code-review
Review code for quality, bugs, security issues, and suggest improvements. Use when asked to review, audit, or improve code. - 100code-review
Review code changes for bugs, security holes and regressions before they merge. Use when the user says "review my changes", "review this PR", "check this diff", "is this safe to merge", or names a branch, commit or files to look over.