sc-pr-check
Skill19 starsChanged 8 months agoMITView on GitHub
Run all local CI checks before creating a PR with interactive failure remediation. Use when validating code quality before pull requests, running pre-flight checks, or fixing CI failures locally.
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kreighmitchell/SuperClaudeword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- kreighmitchell/SuperClaude★ 4100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-data-engineerSkill
- agent-fullstack-developerSkill
- agent-kubernetes-specialistSkill
- agent-ml-engineerSkill
- agent-performance-engineerSkill
- agent-react-specialistSkill
- agent-security-engineerSkill
- agent-technical-writerSkill
- ask-multiSkill
- askSkill
- learned-skills-indexSkill
- sc-analyzeSkill
- sc-brainstormSkill
- sc-buildSkill
- sc-cicd-setupSkill
- sc-code-reviewSkill
- sc-designSkill
- sc-documentSkill
- sc-e2eSkill
- sc-estimateSkill
- sc-evaluateSkill
- sc-explainSkill
- sc-gitSkill
- sc-implementSkill
- sc-improveSkill
- sc-log-fixSkill
- sc-mcpSkill
- sc-pr-fixSkill
- sc-principlesSkill
- sc-pushSkill
- sc-readmeSkill
- sc-researchSkill
- sc-tddSkill
- sc-testSkill
- sc-workflowSkill
- sc-worktreeSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run comprehensive local CI checks before PR creation.
- Distinctive: line 33
Execute: - Run checks sequentially, streaming output
- Distinctive: line 35
Re-run: - After fixes, re-run all checks until green or user stops
- Distinctive: line 104
Run checks in dependency order:
- Distinctive: line 127
When a check fails, identify the failure type and offer targeted fixes.
- Distinctive: line 189
After applying any fix:
- Distinctive: line 265
Read: - Read failing test files, security findings
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pre-PR Check Skill
Run comprehensive local CI checks before PR creation. Auto-detects project tooling, runs all checks, and offers interactive fixes on failure.
Quick Start
# Run all detected checks
/sc:pr-check
# Run specific check categories
/sc:pr-check --only lint,test
# Quick mode - skip slow checks (e2e, security)
/sc:pr-check --quick
# Fix mode - auto-fix what's possible
/sc:pr-check --fix
# Dry run - show what would be checked
/sc:pr-check --dry-runBehavioral Flow
- Detect - Identify project tooling (language, linter, formatter, test runner, security scanner)
- Plan - Build check sequence based on detected tools
- Execute - Run checks sequentially, streaming output
- Remediate - On failure, offer interactive fixes per check type
- Re-run - After fixes, re-run all checks until green or user stops
- Report - Summary of results and fixes applied
Flags
| Flag | Type | Default | Description |
--only | string | all | Comma-separated: lint, format, test, security, types, e2e, build |
--quick | bool | false | Skip slow checks (e2e, security scan) |
--fix | bool | false | Auto-fix fixable issues without prompting |
--dry-run | bool | false | Show detected checks without running |
--strict | bool | false | Treat warnings as errors |
Phase 1: Project Tooling Detection
Auto-detect the project's tooling by examining config files and package manifests.
Detection Matrix
| Check Type | Python | JavaScript/TypeScript | Go | Rust |
| Linter | ruff, flake8, pylint | eslint, biome | golangci-lint | clippy |
| Formatter | ruff format, black | prettier, biome | gofmt | rustfmt |
| Types | mypy, pyright | tsc | (built-in) | (built-in) |
| Tests | pytest, unittest | jest, vitest, mocha | go test | cargo test |
| Security | bandit, pip-audit | npm audit, snyk | govulncheck | cargo audit |
| Build | - | tsc, vite build | go build | cargo build |
| E2E | - | playwright, cypress | - | - |
Detection Strategy
# Python detection
[ -f "pyproject.toml" ] || [ -f "setup.py" ] || [ -f "requirements.txt" ]
# JavaScript/TypeScript detection
[ -f "package.json" ] || [ -f "tsconfig.json" ]
# Go detection
[ -f "go.mod" ]
# Rust detection
[ -f "Cargo.toml" ]
# Check for specific tools in config files
grep -q "ruff" pyproject.toml 2>/dev/null # Ruff
[ -f ".eslintrc*" ] || grep -q "eslint" package.json 2>/dev/null # ESLintDetection Output
## Project Tooling Detected
| Category | Tool | Config | Status |
|----------|------|--------|--------|
| Language | Python 3.12 | pyproject.toml | OK |
| Linter | Ruff | pyproject.toml [tool.ruff] | OK |
| Formatter | Ruff Format | pyproject.toml [tool.ruff] | OK |
| Type Check | mypy | pyproject.toml [tool.mypy] | OK |
| Tests | pytest | pyproject.toml [tool.pytest] | OK |
| Security | bandit | .bandit | OK |
| E2E | playwright | playwright.config.ts | OK |
Running 7 checks...Phase 2: Check Execution
Run checks in dependency order:
| Step | Check | Rationale |
| 1 | Linter | Catch syntax/style errors first (fastest) |
| 2 | Formatter | Ensure consistent formatting |
| 3 | Type checker | Catch type errors before runtime |
| 4 | Unit/Integration tests | Verify correctness |
| 5 | Security scan | Catch vulnerabilities |
| 6 | Build | Verify compilation |
| 7 | E2E tests | Full integration (slowest, skipped with --quick) |
Execution Pattern
For each check:
- Display step number and check name:
[1/7] Running Ruff linter... - Execute the command with timeout
- Capture exit code and output
- On success: show green checkmark, move to next
- On failure: enter remediation flow
Phase 3: Interactive Remediation
When a check fails, identify the failure type and offer targeted fixes.
Lint Failures
[1/7] Ruff linter... FAILED (3 errors)
src/api/routes.py:15:1 F401 unused import
src/models/user.py:8:5 E712 comparison to True
src/utils/helpers.py:22:80 E501 line too long
Actions:
[f] Auto-fix with `ruff check . --fix` (fixes 2 of 3)
[m] Manually fix remaining issues
[s] Skip and continue
[q] QuitTest Failures
[4/7] Tests... FAILED (2 failures)
FAILED tests/test_api.py::test_create_user - AssertionError
FAILED tests/test_auth.py::test_login_expired - TimeoutError
Actions:
[a] Analyze and fix failing tests
[r] Re-run failed tests only
[s] Skip and continue
[q] QuitSecurity Failures
[5/7] Security scan... FOUND 2 issues
HIGH: SQL injection risk in src/api/users.py:45 (B608)
LOW: Assert used in production code src/utils/debug.py:12 (B101)
Actions:
[a] Analyze and remediate issues
[i] Show details for each finding
[s] Skip and continue
[q] QuitFix Type Reference
| Check | Auto-fixable | Manual Fix Needed |
| Lint | Most style issues | Logic errors, unused code decisions |
| Format | All formatting | None |
| Types | None | Type annotations, casts |
| Tests | Some assertion fixes | Logic bugs, mock updates |
| Security | Some patterns | Architecture changes |
| Build | Dependency installs | Code errors |
| E2E | Selector updates | Flow changes |
Phase 4: Re-run After Fixes
After applying any fix:
- Re-run all checks (not just the failed one)
- Continue the fix loop until all pass or user quits
- Track all fixes applied during the session
Phase 5: Results Report
## PR Check Results
**Status**: ALL PASSED | X FAILED
**Duration**: Ns
### Check Results
| Step | Check | Status | Duration |
|------|-------|--------|----------|
| 1/7 | Ruff linter | PASSED | 1.2s |
| 2/7 | Ruff formatter | PASSED | 0.8s |
| 3/7 | Type check | PASSED | 3.4s |
| 4/7 | Tests (48 passed) | PASSED | 12.1s |
| 5/7 | Security scan | PASSED | 2.3s |
| 6/7 | Build | PASSED | 5.6s |
| 7/7 | E2E tests | SKIPPED | --quick |
### Fixes Applied (if any)
- Auto-fixed 3 lint errors (ruff --fix)
- Fixed test assertion in test_create_user
- Remediated B608 SQL injection in users.py
### Next Steps
- Run `/sc:git commit` to commit changes
- Run `/sc:readme` to update documentation
- Create PR with `gh pr create`MCP Integration
PAL MCP
| Tool | When to Use | Purpose |
mcp__pal__debug | Test failures | Root cause analysis for failing tests |
mcp__pal__codereview | Security findings | Validate security remediation |
mcp__pal__precommit | Final validation | Multi-model pre-commit check |
PAL Usage Patterns
# Pre-commit validation after all checks pass
mcp__pal__precommit(
path="/path/to/repo",
step="Validating all changes before PR",
findings="Lint, test, security, type check results",
confidence="high"
)
# Debug complex test failure
mcp__pal__debug(
step="Investigating intermittent test failure in test_auth",
hypothesis="Race condition in async test setup",
confidence="medium"
)Rube MCP
| Tool | When to Use | Purpose |
mcp__rube__RUBE_MULTI_EXECUTE_TOOL | Notifications | Post results to Slack, update Jira |
Tool Coordination
- Bash - Execute linters, formatters, test runners, security scanners
- Glob - Detect config files for tooling identification
- Grep - Parse failure output, find config patterns
- Read - Read failing test files, security findings
- Edit - Apply auto-fixes
Related Skills
/sc:test- Detailed test execution and coverage/sc:log-fix- Debug from log analysis/sc:git- Git workflow operations/sc:analyze- Deeper code quality analysis
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

