Coding guidelines for the django-google-sso library. Enforces PEP 8, type hints, semantic commits, and pytest best practices.
Guidelines for contributing to the django-google-sso library, which adds Google Authentication to Django Admin.
Follow these standards when writing code:
1. **Indentation**: Use four spaces (never tabs)
2. **PEP 8 Compliance**: Follow all PEP 8 guidelines
3. **Line Length**: 92 characters (unless overridden in pyproject.toml)
4. **Formatting**: Run `pre-commit run --all` before committing
5. **Code Formatter**: Use `black` for automatic formatting
Always use type annotations:
Use pytest with these practices:
Follow semantic versioning with one-line commits:
| Prefix | Use When |
|--------|----------|
| `feat:` | New code added to both `./django_google_sso` and unit tests |
| `fix:` | Changes only to code inside `./django_google_sso` |
| `chore:` | Changes to files outside `./django_google_sso` |
| `ci:` | Changes only to `pyproject.toml` |
| `docs:` | Changes only to `./docs` or README |
| `refactor:` | Changes to `./django_google_sso` without test changes |
| `BREAKING CHANGE:` | Changes to minimum Python version in `pyproject.toml` |
For project-specific guidelines, check the local file at `.junie/guidelines.md` in the repository.
Leave a review
No reviews yet. Be the first to review this skill!
# Download SKILL.md from killerskills.ai/api/skills/django-google-sso-development/raw