trace-mcp-pre-commit
/trace-mcp-pre-commit
Run trace-mcp security, quality-gate, and antipattern checks before committing or opening a PR. Activate when the agent is about to create a commit or pull request in a project indexed by trace-mcp.
- Author
- nikolai-vysotskyi ↗
- Repository
- trace-mcp ↗
- Licence
- MIT
- Last repository change
- 13.11.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 13.11.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
Run trace-mcp security, quality-gate, and antipattern checks before committing or opening a PR. Activate when the agent is about to create a commit or pull request in a project indexed by trace-mcp.
Original author description
Run trace-mcp security, quality-gate, and antipattern checks before committing or opening a PR. Activate when the agent is about to create a commit or pull request in a project indexed by trace-mcp.
How it works
- When to Use
- Checklist
- Fix or Escalate
- After Commit
SKILL.md preview
---
name: trace-mcp-pre-commit
description: Run trace-mcp security, quality-gate, and antipattern checks before committing or opening a PR. Activate when the agent is about to create a commit or pull request in a project indexed by trace-mcp.
---
# trace-mcp — Pre-Commit & Pre-PR Checks
Before creating a commit or opening a pull request, run the trace-mcp validation suite. Fix any critical or high findings before committing.
## When to Use
- The user asks to commit, stage, or push changes
- The user asks to open a PR
- The agent has finished implementing a feature or fix and is about to hand off
## Checklist
### 1. Security scan
```
scan_security({ rules: ["all"] })
```
OWASP Top-10 vulnerability scan across the changed scope. If the change touches untrusted data flows, add:
```
taint_analysis({})
```
Trace untrusted sources to sensitive sinks (SQL, shell, file system, HTTP).
### 2. Quality gates on the changed scope
```
check_quality_gates({ scope: "changed" })
```
Validates complexity, coverage, duplication, and any project-configured gates on only the files you changed.
### 3. Antipattern scan
```
detect_antipatterns({})
```
Flags N+1 queries, eager loading, inefficient iteration, and language-specific performance footguns.
### 4. Symbol-level diff for the PR description
```
compare_branches({ branch: "current" })
```
Produces a symbol-level diff (functions added/removed/modified, signatures changed, exports changed). Use this as the basis for an accurate PR description instead of a raw line diff.
### 5. Bug prediction (optional, for risky changes)
```
predict_bugs({})
get_risk_hotspots({})
```
Flags files where the combination of high complexity and high churn makes regressions likely. If your change touches a hotspot, add extra tests.
## Fix or Escalate
- **Critical / High findings:** fix before committing. Do not suppress without discussion.
- **Medium findings:** fix if cheap, otherwise note in the PR description.
- **Low / Info findings:** note in the PR description.
## After Commit
If the commit is part of a larger series, consider:
```
get_changed_symbols({ since: "<base-ref>" })
```
to generate an accurate changelog entry grounded in the symbol graph rather than commit messages.
Versions
The database has no other skills named trace-mcp-pre-commit.
Database snapshot: 13.11.2026 · package version 08aac7882ba8 (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
- 100pre-commit
Full validation gate before committing — quality checks, tests, coverage, security scan, changelog, and companion review. Use right before a commit to verify code is ready. Trigger on "pre-commit", "validate before commit", "ready to commit", "run all checks". - 100validating-pre-commit
Runs quality gate checks before commit or push. Use when preparing to commit, reproducing CI failures locally, or validating changes pass all checks. - 100trace-mcp
Use trace-mcp tools for code navigation, impact analysis, and framework-aware queries instead of Read/Grep/Glob/Bash. Activate whenever the agent needs to explore, understand, or modify a codebase that has trace-mcp indexed. - 100pre-commit-quality-review
Use when the user asks to commit, amend, or squash code, or requests a pre-commit structural quality review. - 100pre-commit-review
Review local staged and unstaged tracked-file changes before committing or before a pull request exists. Use when the user invokes /pre-commit-review, asks for a pre-commit review, asks to review local changes before commit, or wants a local working-tree review before a PR exists. - 100pre-commit-review
Review staged and unstaged changes before committing. Use when asked for a pre-commit review, a code-quality review of the current diff, or when a solve workflow requests an independent review.