run-pre-commit-checks — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited run-pre-commit-checks (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill defines the mandatory checks that must pass before any commit.
All three checks must pass before committing:
npm run lintWhat it checks:
eslint.config.mjsTo auto-fix issues:
npm run lint -- --fixnpm run compile-testsWhat it checks:
Output location: out/ directory (not used for production)
npm run unittestWhat it checks:
src/test/ passbuild/.mocha.unittests.json# Run all checks in sequence
npm run lint
npm run compile-tests
npm run unittest
# If all pass, commit
git add -A
git commit -m "feat: your change description (Fixes #N)"| Error | Fix |
|---|---|
@typescript-eslint/no-unused-vars | Remove unused variable or prefix with _ |
import/order | Run npm run lint -- --fix |
@typescript-eslint/no-explicit-any | Add proper type annotation |
no-console | Use traceLog/traceVerbose instead of console.log |
| Error | Fix |
|---|---|
TS2339: Property does not exist | Check property name or add type guard |
TS2345: Argument type not assignable | Check function parameter types |
TS2322: Type not assignable | Add type assertion or fix type mismatch |
TS18048: possibly undefined | Add null check or use optional chaining |
The maintainer agent workflow requires:
Code Change → Reviewer Agent → Pre-Commit Checks → Commit
↓
Fix Issues → Re-run Reviewer → Pre-Commit ChecksNever skip pre-commit checks. They catch:
These checks should also be run:
The hooks system can automate running lint after file edits (see .github/hooks/).
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.