Slash Command

/quality-validation

Runs automated quality checks including linting, testing, build/type-check, dependency audits, and security scans for Node.js or Python projects.

Node

Python

code-quality

security

npx claudepluginhub fradser/dotclaude --plugin github

Details

Namespacecreate-pr/references/

Prompt Preview

# Quality Validation Process

## Node.js Projects

Run the following validation commands:

- **Lint**: `npm run lint` or `pnpm lint`
- **Test**: `npm test` or `pnpm test`
- **Build**: `npm run build` or `pnpm build`
- **Type Check**: `npm run type-check` or `pnpm type-check`

Validate package.json changes and check for security vulnerabilities using `npm audit` or `pnpm audit`.

## Python Projects

Run the following validation commands:

- **Format**: `black .` or `ruff format`
- **Lint**: `ruff check .`
- **Test**: `pytest` or `python -m pytest`
- **Type Check**: `mypy .`

Validate require...

Command Content

Other plugins with /quality-validation

/check

2.7k

Runs project validation checks like lint/test across JavaScript/TypeScript, Python, Go, Rust, Ruby and auto-fixes errors without committing changes.

3 tools

all-commands

/verify

3.5k

Runs verification checks on codebase including types (mypy), lint (ruff), tests (pytest cov), security (pip-audit), secrets, prints, and git status. Outputs summary report with pass/fail and readiness status.

claude-scholar

/security-scan

1.3k

Scans codebase for hardcoded secrets, vulnerable dependencies, code patterns like injections/XSS, and config issues. Produces structured report with issues, severities, and remediation steps.

project-starter

/code-review

681

Reviews uncommitted code changes via git diff for security vulnerabilities like hardcoded secrets and SQL injection, plus quality issues, generating a severity-based report with line numbers, descriptions, and fixes. Blocks commits on critical/high issues.

claude-forge

Stats

Parent Repo Stars512

Parent Repo Forks39

Last CommitFeb 1, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

# Quality Validation Process ## Node.js Projects Run the following validation commands: - **Lint**: `npm run lint` or `pnpm lint` - **Test**: `npm test` or `pnpm test` - **Build**: `npm run build` or `pnpm build` - **Type Check**: `npm run type-check` or `pnpm type-check` Validate package.json changes and check for security vulnerabilities using `npm audit` or `pnpm audit`. ## Python Projects Run the following validation commands: - **Format**: `black .` or `ruff format` - **Lint**: `ruff check .` - **Test**: `pytest` or `python -m pytest` - **Type Check**: `mypy .` Validate require...

Quality Validation Process

Node.js Projects

Run the following validation commands:

Lint: npm run lint or pnpm lint

Test: npm test or pnpm test

Build: npm run build or pnpm build

Type Check: npm run type-check or pnpm type-check

Validate package.json changes and check for security vulnerabilities using npm audit or pnpm audit.

Python Projects

Run the following validation commands:

Format: black . or ruff format

Lint: ruff check .

Test: pytest or python -m pytest

Type Check: mypy .

Validate requirements and dependencies, and check for security issues using pip-audit or similar tools.

Security Validation

Comprehensive security scanning must include:

Scan for sensitive files (.env, .key, .pem, credentials.json, etc.)

Check for hardcoded secrets, passwords, API tokens

Validate input sanitization in changed files

Ensure no credentials in commit history

Use tools like gitleaks or trufflehog for secret scanning