mirror of
https://github.com/jjbrunton/Sauci.git
synced 2026-10-31 18:19:43 +00:00
Jamie BruntonandClaude Code
f7aa6ed8dd
Introduce feature_interests schema + realtime publication and surface opt-in trends in the admin dashboard. Add Jest test infrastructure/coverage for the mobile app and update push-all to run mobile checks before pushing. Co-authored-by: Claude Code <claude@anthropic.com>
2.2 KiB
2.2 KiB
description, allowed-tools
| description | allowed-tools |
|---|---|
| Security check, run checks, commit, and push | Bash(git status:*), Bash(git diff:*), Bash(git log:*), Bash(git add:*), Bash(git commit:*), Bash(git push:*), Bash(git branch:*), Bash(npm:*) |
Context
- Current branch: !
git branch --show-current - Git status: !
git status --short - Staged changes: !
git diff --cached --stat - Unstaged changes: !
git diff --stat
Your Task
Perform a secure commit and push with the following steps:
Step 1: Security Check
Before committing, scan the staged changes for potential secrets or sensitive data:
- API keys, tokens, or credentials (patterns like
sk-,api_key,secret,password,token,bearer) .envfiles or environment variable files with actual values- Private keys or certificates
- Database connection strings with credentials
- Hardcoded URLs with authentication parameters
Run git diff --cached to inspect what will be committed. If you find ANY potential secrets:
- STOP immediately
- List the specific files and lines containing potential secrets
- Do NOT proceed with the commit
- Suggest how to fix (use environment variables, add to .gitignore, etc.)
Step 2: Stage All Changes
If security check passes, stage all changes with git add -A.
Step 3: Run Checks
Before committing, make sure checks pass for the projects you touched:
- Mobile typecheck:
npm --prefix apps/mobile run typecheck - Mobile tests:
npm --prefix apps/mobile run test:ci - Web typecheck (if you changed
apps/web):npm --prefix apps/web run typecheck
Note: apps/supabase is Supabase config/functions (no TS typecheck).
If any command fails, STOP and report the output.
Step 4: Generate Commit Message
Analyze the changes and create a concise, meaningful commit message that:
- Summarizes what changed (not how)
- Uses imperative mood ("Add feature" not "Added feature")
- Is 50 chars or less for the subject line
- Includes the standard Claude Code footer
Look at recent commits with git log --oneline -5 to match the repository's commit style.
Step 5: Commit and Push
- Create the commit with the generated message
- Push to the remote repository
If any step fails, report the error and stop.