메뉴
Quality tooling awareness for projects. Covers linting, formatting, type checking, testing, dead code detection, and pre-commit hooks. Use when reviewing code, setting up projects, or noticing missing quality tooling.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/simpleapps-com/augur-skills --skill quality명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
Basecamp 2 integration via MCP. Covers MCP tool reference, URL parsing, authentication, Chrome fallback, attachments, and site-info documents. Use when reading or writing Basecamp data.
Bash command conventions. One command per call, use dedicated tools over shell equivalents, check wiki for approved commands. Load this skill before running Bash commands.
When working in load-bearing code (the 5-10% where correctness matters most: money math, auth, concurrency, state machines, security boundaries), tighten the type system first, then add formal contracts (@requires/@ensures/@invariant/@trusted) in the host language's native comment syntax. Use Unicode glyphs (∀, ∈, ≥, ℕ) for AI priming, paired with ASCII gloss for human readers. The contracts pay off through three independent mechanisms: priming agent reasoning, surfacing tests, and adding context-window value that agents themselves report. Drift between contract and code is a defect.
| name | quality |
| description | Quality tooling awareness for projects. Covers linting, formatting, type checking, testing, dead code detection, and pre-commit hooks. Use when reviewing code, setting up projects, or noticing missing quality tooling. |
These tools keep codebases healthy. When working in a project, check whether they are configured. If any are missing, suggest them to the user.
| Tool | Purpose | Config files | Run command |
|---|---|---|---|
| ESLint | Catch bugs and enforce patterns | .eslintrc*, eslint.config.* | pnpm lint |
| Prettier | Consistent formatting | .prettierrc*, prettier.config.* | pnpm format |
| TypeScript | Type safety | tsconfig.json | pnpm typecheck |
| Vitest / Jest | Tests | vitest.config.*, jest.config.* | pnpm test |
| knip | Dead code: unused exports, deps, and files | knip.json, knip.ts | pnpm knip |
| Lefthook | Pre-commit hooks: run checks before push | lefthook.yml | auto on commit |
Also check repo/package.json for scripts containing: lint, format, typecheck, test, check, validate.
Check repo/composer.json for scripts. Look for PHPStan (static analysis), PHP-CS-Fixer (formatting), PHPUnit (tests).
Check repo/pyproject.toml or repo/setup.cfg. Look for ruff (lint/format), black (formatting), mypy (types), pytest (tests).
Every project SHOULD have at minimum: lint, format, test. Increasingly, dead code detection (knip) and pre-commit hooks (lefthook) are expected.
If any are missing, flag them:
Missing quality tooling:
- [ ] Linting: suggest eslint / ruff / phpstan
- [ ] Formatting: suggest prettier / black / php-cs-fixer
- [ ] Testing: suggest vitest / pytest / phpunit
- [ ] Dead code detection: suggest knip
- [ ] Pre-commit hooks: suggest lefthook
Do not install or configure tools without the user's approval. Flag what's missing and explain why it helps. Let the user decide.
Projects SHOULD target the current Active LTS of their language runtime. Maintenance LTS is acceptable. EOL runtimes SHOULD be flagged.
Runtime freshness is advisory, not a hard failure. Legitimate exceptions exist: libraries with documented compatibility policies, hosting-locked client projects, migration-in-progress repos. Surface findings as a prompt and let the user decide.
Check the current LTS from the language's official schedule, not memory (LTS designations rotate each October):
.github/workflows/*.ymlengines in package.jsonpython_requires in pyproject.toml / setup.pyrequire or config.platform.php in composer.json"CI matrix includes Node 18 (EOL). Current Active LTS is Node 24. Drop EOL and add current LTS?"
If the user cites a constraint (hosting, compatibility, library support policy), record it in the project's wiki so future sessions see the exception and skip the prompt.
engines pins an EOL runtime: suggest dropping it and adding current Active LTSSee work-habits: "Leave it better than you found it" and "Resolve, never hide." Both apply fully to quality checks. Fix every issue regardless of who introduced it. NEVER suppress checks. Fix the code.
When reviewing code, scan for existing suppressions (eslint-disable, @ts-ignore, .skip, noqa, phpcs:ignore, etc.) and flag every instance to the user. These are hidden technical debt.
In pnpm workspace projects, the root pnpm-lock.yaml and site-level lockfiles MUST stay in sync. CI uses --frozen-lockfile and will reject mismatched lockfiles. This is the most common cause of deploy failures.
After ANY pnpm install, pnpm update, or pnpm add in a workspace, run pnpm install at the repo root to regenerate the root lockfile. Commit both lockfiles together. If you forget, the next deploy will fail.
Use the /quality command to discover and run all configured checks. It handles the full cycle: discover, run, fix, repeat until clean.