project-policies
Check and enforce project policies from CLAUDE.md and POLICIES.md. Use when validating implementations against project standards, checking code style requirements, or ensuring compliance with development guidelines.
When & Why to Use This Skill
This Claude skill automates the enforcement of project-specific guidelines by analyzing CLAUDE.md and POLICIES.md. It ensures that code implementations, Git workflows, and testing procedures align with established developer standards, reducing manual review overhead and maintaining high code quality through automated compliance checks.
Use Cases
- Automated PR Readiness Check: Use the skill to verify that your current branch, commit messages, and code patterns meet all project requirements before submitting a pull request.
- Git Workflow Enforcement: Prevent common mistakes such as direct commits to the main branch and ensure adherence to specific feature-branch naming conventions.
- Standardized Testing Compliance: Automatically validate that new features or bug fixes are accompanied by the necessary tests and that all pre-commit hooks have been successfully executed.
- Project Onboarding: Help new developers quickly align with the project's unique coding styles, architectural patterns, and workflow policies defined in the local documentation.
| name | project-policies |
|---|---|
| description | Check and enforce project policies from CLAUDE.md and POLICIES.md. Use when validating implementations against project standards, checking code style requirements, or ensuring compliance with development guidelines. |
| allowed-tools | Read, Glob, Grep |
Project Policies
Ensure implementations comply with project guidelines.
Policy Documents
CLAUDE.md- Development guidelines, code patterns, testing strategyPOLICIES.md- User policies and developer workflow guidelines
Key Policies
Git Workflow
- Never commit directly to
main - Use feature branches:
feature/<issue>-<description> - Commit format:
#<issue>: <type>: <description>
Code Quality
- Pre-commit hooks must pass
- Follow existing code patterns
Testing
- New features need tests
- Bug fixes need regression tests
Compliance Checklist
Before submitting PR:
- On feature branch (not main)
- Commit messages follow convention
- Pre-commit hooks pass
- Tests pass
- No security vulnerabilities
- Follows existing code patterns
Verify Compliance
# Verify branch
git branch --show-current # Should NOT be 'main'
# Verify pre-commit
pre-commit run --all-files
# Verify tests
cd backend && uv run pytest tests/ -v
Policy Violations
Critical (Must Fix): Committing to main, skipping hooks, breaking tests, security issues
Warning (Should Fix): Missing tests, outdated docs, non-standard commits