From trace-mcp
Runs trace-mcp pre-commit/PR checks: security scans (OWASP, taint analysis), quality gates on changed files, antipattern detection, symbol diffs, and bug predictions before committing or opening PRs.
npx claudepluginhub nikolai-vysotskyi/trace-mcp --plugin trace-mcpThis skill uses the workspace's default tool permissions.
Before creating a commit or opening a pull request, run the trace-mcp validation suite. Fix any critical or high findings before committing.
Runs mechanical pre-commit checks (lint, typecheck, tests via pnpm/npm/make/tsc) first, then AI review if passed. Blocks commits on failures for fast local feedback.
Performs structured code reviews checking requirements, quality, and security standards after changes or before merge. Uses git diffs, context snapshots, and blast radius for scope.
Pre-commit quality gate validating logic correctness, error handling, regressions, and completeness in code changes. Auto-fires before commit via cook or on large diffs.
Share bugs, ideas, or general feedback.
Before creating a commit or opening a pull request, run the trace-mcp validation suite. Fix any critical or high findings before committing.
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).
check_quality_gates({ scope: "changed" })
Validates complexity, coverage, duplication, and any project-configured gates on only the files you changed.
detect_antipatterns({})
Flags N+1 queries, eager loading, inefficient iteration, and language-specific performance footguns.
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.
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.
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.