Menu
Git commit message conventions and branch naming standards for Nudge. Use when creating commits, branches, or preparing code for version control. Triggers on commit creation, branch creation, or when user asks about git workflow conventions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Development workflow and Docker commands for Nudge. Use when setting up the environment, debugging containers, running Django management commands, or installing dependencies. Triggers when the user asks about development setup, Docker, or environment issues.
Backend architecture patterns and conventions for Nudge. Use when creating or modifying Django models, views, serializers, URLs, or Celery tasks. Triggers when working on backend code or when the user asks about backend conventions.
Django admin customization patterns for Nudge. Use when modifying the admin panel, adding models to admin, or changing admin branding/styling. Triggers when the user asks about Django admin, admin panel, or model registration.
Frontend architecture patterns and conventions for Nudge. Use when creating or modifying React components, pages, API calls, i18n, or CSS modules. Triggers when working on frontend code or when the user asks about frontend conventions.
Testing discipline for Nudge — write strict tests, fail hard when they reveal bugs, diagnose and fix the root cause (code, infra, or test), then re-run until green. Use whenever writing or running tests (unit, integration, E2E), debugging a failing test, or tempted to reach for `test.skip` / weakened assertions / `expect.anything()` / "known pre-existing failure" labels.
| name | git-conventions |
| description | Git commit message conventions and branch naming standards for Nudge. Use when creating commits, branches, or preparing code for version control. Triggers on commit creation, branch creation, or when user asks about git workflow conventions. |
<type>: <subject>
<bullet points explaining what changed and why>
feat, fix, chore, docs, refactor, test, stylegit config user.name and git config user.email. When amending, use --reset-author to update to current PC config.feat/<slug> # new feature
fix/<slug> # bug fix
chore/<slug> # maintenance, refactor, tooling
Examples: feat/lot-selection-modal, fix/push-token-refresh, chore/docker-hardening
main is protected — direct push is rejected. Always:
git checkout -b <type>/<slug>
git push -u origin <type>/<slug>
gh pr create --title "<concise title>" --body "..."
Never push --force. If there are conflicts, resolve with merge.
The project has a pre-commit hook (scripts/pre-commit) that runs:
ruff check + ruff format --check on backend (Python)prettier --check + eslint on frontend (JS/JSX)If the hook fails, fix the issue and create a NEW commit (never --amend).
To format before committing:
docker compose -f dev/docker-compose.yml exec backend ruff format .docker compose -f dev/docker-compose.yml exec frontend npm run formatfeat: reorganize URL namespaces, Django admin branding, and UX improvements
URL namespaces:
- Move app prefixes (api/health/, api/auth/, api/push/) to root urls.py
- Strip duplicate prefixes from each app's urls.py
Django admin:
- Custom branding with Nudge indigo color scheme
- Add LocaleMiddleware for multilingual admin (en/es/gl)
Push notifications:
- Enable VitePWA service worker in dev mode
- Add @csrf_exempt to admin_access view