firm-alias-commit-author
Commits are authored under a firm or team alias instead of a specific person
Applies to: Project-level
Why this matters
When a commit shows up in git blame, the team should be able to tell which human wrote it so they can ask questions, review edge cases, or assign ownership. Shared identities like "embi-dev" or "acme-team" hide who actually did the work — especially when the work is done by a contracting firm. Individual handles are fine, and bots committing under bot names are fine; the problem is people hiding behind the firm's name.
Catch it before it ships
pip install stablestack # or: npx stablestackstablestack # scans your project, PROJ006 includedstablestack explain PROJ006False positive in your codebase? Suppress a single line with # noqa: PROJ006
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
PROJ003pyright-config
Project should have a pyright configuration with sensible defaults.
PROJ004beta-dependencies
Pre-release dependency may have stability issues
PROJ005gitignored-claude-md
CLAUDE.md should not be gitignored — it belongs in version control.
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.