pyright-config
Project should have a pyright configuration with sensible defaults.
Applies to: Project-level
Why this matters
Pyright's default settings are too strict for most projects, causing noise that discourages adoption. A well-tuned pyrightconfig.json or pyproject.toml [tool.pyright] section enables useful type checking without overwhelming beginners. stablestack recommends a balanced configuration that catches real bugs without pedantry.
Catch it before it ships
pip install stablestack # or: npx stablestackstablestack # scans your project, PROJ003 includedstablestack explain PROJ003PROJ003 is part of the Pro rule set. See pricing — the free tier ships 24 checks with no signup.
False positive in your codebase? Suppress a single line with # noqa: PROJ003
More Project Setup checks
missing-ai-context-file
Projects edited by AI assistants should ship a context file (CLAUDE.md, AGENTS.md, .cursorrules, or equivalent)
PROJ002missing-git
Projects should use git for version control
PROJ004beta-dependencies
Pre-release dependency may have stability issues
PROJ005gitignored-claude-md
CLAUDE.md should not be gitignored — it belongs in version control.
PROJ006firm-alias-commit-author
Commits are authored under a firm or team alias instead of a specific person
PROJ007low-test-coverage-ratio
Codebase has a large amount of hand-written source code but very few automated tests
PROJ008macos-fork-safety-missing
Shell script starts gunicorn/uvicorn/flask with reload but doesn't export OBJC_DISABLE_INITIALIZE_FORK_SAFETY — macOS devs will see 'Python quit unexpectedly' popups on every worker reload.