Use this file to discover all available pages before exploring further.
Jazz helps you automate repetitive development tasks, from generating commit messages to running security audits. Use Jazz to handle git workflows, code reviews, technical debt tracking, and more.
You: Read my uncommitted changes, commit them with a short and long commit message, then pushAgent: [Checking git status...]Found 3 modified files:- src/auth/jwt.ts- src/middleware/auth.ts- tests/auth.test.ts[Analyzing changes...]Suggested commit message:Short: "feat: implement JWT token refresh with rotation"Long:"Add automatic token refresh mechanism that refreshes tokens5 minutes before expiration. Implements single-use refresh tokenrotation for enhanced security. Adds Redis caching for refreshtoken blacklist to prevent replay attacks.- Add automatic refresh 5min before expiration- Implement single-use refresh token rotation- Add Redis caching for refresh token blacklist- Add 12 new tests covering refresh flow"Should I commit and push? (yes/no): yesAgent: ✓ Committed successfully ✓ Pushed to origin/main
Jazz automatically detects conventional commit message formats and will show you exactly what will be committed before proceeding.
You: I'm about to create a PR. Generate a description from my changesAgent: [Analyzes git diff and commits]Found changes in:- src/auth/jwt.ts (token refresh logic)- src/middleware/auth.ts (new middleware)- tests/auth.test.ts (12 new tests)Generated PR description:---## SummaryImplements JWT token refresh mechanism to improve user experience and security.## Changes- ✨ Add automatic token refresh before expiration- 🔒 Implement refresh token rotation for security- 🧪 Add comprehensive test coverage (12 new tests)- 📝 Update authentication documentation## Technical Details- Tokens now refresh 5 minutes before expiration- Refresh tokens are single-use and rotate on each refresh- Added Redis caching for refresh token blacklist- Backward compatible with existing auth flow## Testing- All existing tests passing- New tests cover refresh flow, rotation, and edge cases- Manual testing completed on staging## Breaking ChangesNone - fully backward compatible## Checklist- [x] Tests added/updated- [x] Documentation updated- [x] No breaking changes- [x] Tested locally---Copy this to your PR?You: yesAgent: ✓ Copied to clipboardReady to paste into GitHub!
You: Scan the codebase for security issues and fix critical onesAgent: 🔒 Security Audit Report🔴 Critical Issues (2):1. Hardcoded API Key (src/config/api.ts:12) const API_KEY = "sk_live_abc123..."; Fix: Move to environment variable2. SQL Injection Risk (src/api/search.ts:45) db.query(`SELECT * FROM users WHERE name = '${userName}'`); Fix: Use parameterized queriesShould I fix these automatically?You: yesAgent: [Applies fixes]✓ Moved API key to environment variable✓ Converted to parameterized query✓ Added input sanitization✓ Added tests for malicious input⚠️ Ready to commit security fixes?You: yesAgent: ✓ Committed: "security: fix critical vulnerabilities"
You: Find all TODO comments in src/ and create a prioritized action planAgent: Found 23 TODO comments:🔴 High Priority (5):1. src/auth/jwt.ts:45 - "Add token refresh before security audit"2. src/api/billing.ts:123 - "URGENT - Fix race condition in payments"3. src/db/migrations.ts:67 - "Add rollback support before v2.0"🟡 Medium Priority (12)🟢 Low Priority (6)You: Show me the code for item #2 and suggest a fixAgent: Current code has a race condition in payment processing.Suggested fix:- Use database transaction with row-level locking- Add idempotency key handling- Implement retry logicShould I apply this fix?You: yes, and run testsAgent: ✓ File updated with transaction locking✓ TODO comment removed✓ All tests passing (12/12 payment tests passed)
Jazz can search for various technical debt markers (TODO, FIXME, HACK, XXX, etc.) and prioritizes them based on keywords (URGENT, CRITICAL) and context.
You: Deploy latest main to stagingAgent: Pre-deployment checks...✓ All tests passing on main✓ No pending migrations✓ Latest commit: abc123 "feat: add notifications"Starting staging deployment:Step 1: Build✓ Build successful (2m 34s)Step 2: Database MigrationsFound 2 pending migrations.⚠️ Apply migrations to staging database?You: yesAgent: ✓ Applied migrations successfullyStep 3: Deploy Application⚠️ About to deploy to staging.app.company.comWill cause ~30s downtime. Proceed?You: yesAgent: ✓ Uploaded assets to S3✓ Updated container image✓ Restarted application servers✓ Health check passedStep 4: Smoke Tests✓ Homepage loads (201ms)✓ API health: OK✓ Database connectivity: OK✓ Deployment Complete!Duration: 4m 12s
Jazz runs comprehensive pre-deployment checks and all dangerous operations require explicit approval. Smoke tests verify the deployment was successful.
jazz agent create# Name: dev-assistant# Tools: Git, File System, Shell
Then start chatting:
jazz agent chat dev-assistant
All git operations, file changes, and shell commands require your approval before execution. Jazz will show you exactly what will be executed before proceeding.