cursor-devops-commands 1.0.0

package/commands/deployment/metrics-report.md

@@ -0,0 +1,272 @@
+---
+description: Generate velocity, DORA metrics, AI impact, and ROI report for tickets/sprints
+category: Ops & Monitoring
+aliases: [metrics, velocity, roi-calc, report]
+---
+
+# Metrics Report - Development Velocity & ROI Tracking
+
+Generate measurable business outcomes for engineering work.
+
+## ⚠️ Confidence Bounds
+
+AI-related metrics are **estimated** and **directional**:
+
+-   AI attribution is heuristic-based, not deterministic
+-   Numbers are approximate indicators, not hard KPIs
+-   Use for personal measurement and trend analysis
+-   **Do not** use for performance reviews or metric gaming
+
+## Usage
+
+```
+/metrics-report {TICKET_ID}
+/metrics-report --sprint current
+/metrics-report --team @YourOrg/team-a
+/metrics-report --period 30d
+/roi-calc                              # Alias: AI ROI focus
+```
+
+## What This Does
+
+1. **Collects metrics** - Time, velocity, quality data
+2. **Calculates DORA** - Key engineering metrics
+3. **Tracks AI-assisted work** - Cursor/copilot impact
+4. **Generates ROI** - Business value of changes
+5. **Creates report** - Shareable with leadership
+
+## DORA Metrics (2025 Standard)
+
+| Metric                    | Definition          | Target      |
+| ------------------------- | ------------------- | ----------- |
+| **Lead Time**             | Commit → Production | < 24 hours  |
+| **Deployment Frequency**  | Deploys per day     | > 1 per day |
+| **Change Failure Rate**   | Failed deploy %     | < 5%        |
+| **Mean Time to Recovery** | Incident resolution | < 1 hour    |
+
+## Output Format
+
+```
+📋 Generating metrics report for TICKET-123...
+
+════════════════════════════════════════════════════════════════
+  TICKET SUMMARY
+════════════════════════════════════════════════════════════════
+
+Ticket:      TICKET-123 - Marketing texts for protection packages
+Type:        Story (Feature)
+Priority:    Medium
+Sprint:      2024-12-W51
+
+════════════════════════════════════════════════════════════════
+  ⏱️ VELOCITY METRICS
+════════════════════════════════════════════════════════════════
+
+## Timeline
+
+| Phase | Start | End | Duration |
+|-------|-------|-----|----------|
+| Created | Dec 18 | - | - |
+| In Progress | Dec 20 | Dec 23 | 3 days |
+| In Review | Dec 23 | Dec 23 | 4 hours |
+| Merged | Dec 23 | - | - |
+| Deployed | Dec 23 | - | 2 hours |
+
+## DORA Metrics
+
+| Metric | Value | Target | Status |
+|--------|-------|--------|--------|
+| Lead Time | 5 days | < 7 days | ✅ Good |
+| Cycle Time | 3 days | < 5 days | ✅ Excellent |
+| Review Time | 4 hours | < 8 hours | ✅ Excellent |
+| Time to Deploy | 2 hours | < 4 hours | ✅ Excellent |
+
+## Comparison to Team Average
+
+| Metric | This Ticket | Team Avg | Delta |
+|--------|-------------|----------|-------|
+| Lead Time | 5 days | 7.2 days | -31% ✅ |
+| Lines Changed | 156 | 234 | -33% ✅ |
+| Files Touched | 7 | 12 | -42% ✅ |
+| PR Revisions | 2 | 3.5 | -43% ✅ |
+
+════════════════════════════════════════════════════════════════
+  📊 QUALITY METRICS
+════════════════════════════════════════════════════════════════
+
+## Code Quality
+
+| Metric | Value | Threshold | Status |
+|--------|-------|-----------|--------|
+| Test Coverage | 78% | > 70% | ✅ Pass |
+| Mutation Score | 71% | > 65% | ✅ Pass |
+| Lint Issues | 0 | 0 | ✅ Pass |
+| Type Coverage | 100% | 100% | ✅ Pass |
+
+## Post-Deployment
+
+| Metric | Before | After | Change |
+|--------|--------|-------|--------|
+| Error Rate | 0.02% | 0.02% | 0% ✅ |
+| LCP | 2.1s | 2.1s | 0% ✅ |
+| Bundle Size | 245KB | 246KB | +0.4% ✅ |
+
+## Review Quality
+
+| Metric | Value |
+|--------|-------|
+| Comments | 5 |
+| Blocking issues | 0 |
+| Suggestions | 3 |
+| Approvals | 2 |
+| Time to first review | 45 min |
+
+════════════════════════════════════════════════════════════════
+  🤖 AI-ASSISTED DEVELOPMENT METRICS
+════════════════════════════════════════════════════════════════
+
+## Cursor/Copilot Usage
+
+| Metric | Value |
+|--------|-------|
+| AI-generated code | 42% |
+| AI suggestions accepted | 78% |
+| Commands used | 12 |
+| Time saved (estimated) | 4.5 hours |
+
+## Commands Used
+
+| Command | Times | Outcome |
+|---------|-------|---------|
+| /full-flow | 1 | Workflow orchestration |
+| /gather-context | 2 | Requirements gathering |
+| /pr-review | 1 | Self-review |
+| /jira-test | 1 | How to Test comment |
+| /jira-docs | 1 | Confluence page |
+
+## AI ROI
+
+```
+
+Without AI Assistance (Estimated):
+Development: 16 hours
+Testing: 4 hours
+Documentation: 2 hours
+Total: 22 hours
+
+With AI Assistance (Actual):
+Development: 9 hours
+Testing: 2 hours
+Documentation: 0.5 hours
+Total: 11.5 hours
+
+Time Saved: 10.5 hours (48%)
+
+```
+
+════════════════════════════════════════════════════════════════
+  💰 BUSINESS VALUE
+════════════════════════════════════════════════════════════════
+
+## Feature Impact
+
+| Metric | Value |
+|--------|-------|
+| Users Affected | ~50,000/day |
+| Conversion Impact | TBD (A/B test) |
+| Revenue Impact | TBD (post-rollout) |
+
+## Engineering Investment
+
+| Category | Hours | Cost (est.) |
+|----------|-------|-------------|
+| Development | 11.5 | €1,150 |
+| Review | 1.5 | €150 |
+| Testing | 2 | €200 |
+| **Total** | **15** | **€1,500** |
+
+## ROI Calculation
+
+```
+
+Investment: €1,500 (15 engineer hours)
+Expected Return: €4,500/month (improved conversion)
+Payback Period: ~10 days
+Annual ROI: 3,500%
+
+```
+
+════════════════════════════════════════════════════════════════
+  📈 TRENDS
+════════════════════════════════════════════════════════════════
+
+## Your Velocity (Last 30 Days)
+
+| Week | Tickets | Avg Lead Time | Quality |
+|------|---------|---------------|---------|
+| W49 | 3 | 6.2 days | 92% |
+| W50 | 4 | 5.8 days | 95% |
+| W51 | 3 | 5.0 days | 97% |
+
+Trend: ↑ Improving (+19% velocity, +5% quality)
+
+## Team Comparison
+
+| Developer | Tickets | Velocity | Quality |
+|-----------|---------|----------|---------|
+| You | 10 | ████████ 92% | ██████████ 95% |
+| Team Avg | 8 | ██████ 78% | ████████ 88% |
+
+════════════════════════════════════════════════════════════════
+  📋 EXECUTIVE SUMMARY
+════════════════════════════════════════════════════════════════
+
+## TICKET-123 Metrics at a Glance
+
+| Category | Score | Details |
+|----------|-------|---------|
+| Velocity | ⭐⭐⭐⭐⭐ | 31% faster than average |
+| Quality | ⭐⭐⭐⭐ | 78% coverage, 0 regressions |
+| AI Impact | ⭐⭐⭐⭐⭐ | 48% time saved |
+| Business Value | ⭐⭐⭐⭐ | High (user-facing feature) |
+
+**Key Highlights:**
+- Feature delivered 2 days ahead of estimate
+- Zero production issues post-deploy
+- AI assistance reduced development time by ~50%
+- Comprehensive documentation created automatically
+
+**Recommendation:**
+Continue using AI-assisted workflow for similar tickets.
+Consider as template for team adoption.
+```
+
+## Data Sources
+
+```bash
+# Get ticket timeline from Jira
+jira issue view {TICKET} --plain
+
+# Get PR metrics from GitHub
+gh pr view {PR} --json createdAt,mergedAt,reviews,comments
+
+# Get deployment info
+gh api repos/YourCompany/com.yourcompany.web.public/deployments
+
+# Get code metrics
+git log --oneline --after="2024-12-01" --author="$USER" | wc -l
+
+# Get coverage
+pnpm test:coverage -- --coverageReporters=json-summary
+```
+
+## AI Execution
+
+When user runs `/metrics-report {TICKET}`:
+
+1. **Collect data** - Jira, GitHub, monitoring
+2. **Calculate DORA** - Lead time, deployment freq, etc.
+3. **Track AI usage** - Commands, time saved
+4. **Estimate ROI** - Business value projection
+5. **Compare trends** - Historical performance
+6. **Generate report** - Executive-ready summary

package/commands/deployment/post-deploy-check.md

@@ -0,0 +1,150 @@
+---
+description: Monitor feature health after deploy - errors, metrics, rollout status
+category: Ops & Monitoring
+aliases: [deploy-check, monitor, verify-deploy]
+---
+
+# Post-Deploy Check - Verify Feature Health After Deployment
+
+Monitor and verify the health of a feature after deployment using observability tools.
+
+## Usage
+
+```
+/post-deploy-check {TICKET_ID}
+/post-deploy-check {TICKET_ID} --env production
+/post-deploy-check {TICKET_ID} --duration 30m
+```
+
+## What This Does
+
+1. **Identifies deployed changes** - Maps ticket to deployed commits
+2. **Monitors error rates** - Checks for spikes in Sentry/Instana
+3. **Tracks performance metrics** - Bundle size, LCP, FID
+4. **Validates feature flags** - Confirms Statsig rollout status
+5. **Generates health report** - Pass/Fail with recommendations
+
+## Monitoring Integration
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│  MONITORING SOURCES                                         │
+├─────────────────────────────────────────────────────────────┤
+│  Instana    → Error rates, latency, traces                  │
+│  Sentry     → JavaScript errors, breadcrumbs                │
+│  Statsig    → Feature flag status, experiment results       │
+│  CloudWatch → Lambda metrics, API gateway                   │
+│  GitHub     → Deployment status, commit info                │
+└─────────────────────────────────────────────────────────────┘
+```
+
+## Health Check Dimensions
+
+| Dimension       | Metrics                | Threshold       |
+| --------------- | ---------------------- | --------------- |
+| **Errors**      | Error rate, new errors | < 0.1% increase |
+| **Performance** | LCP, FID, CLS          | No regression   |
+| **Bundle**      | JS size, chunk sizes   | < 5% increase   |
+| **API**         | Latency, 5xx rate      | < p95 baseline  |
+| **Feature**     | Flag status, rollout % | As configured   |
+
+## Output Format
+
+```
+📋 Post-Deploy Check for TICKET-123...
+
+════════════════════════════════════════════════════════════════
+  DEPLOYMENT INFO
+════════════════════════════════════════════════════════════════
+
+Ticket:      TICKET-123 - Marketing texts for protection packages
+Commit:      ed304bcf4fb
+Deployed:    2024-12-23 15:30:00 UTC
+Environment: Production (EU)
+Duration:    30 minutes monitored
+
+════════════════════════════════════════════════════════════════
+  HEALTH METRICS
+════════════════════════════════════════════════════════════════
+
+## Error Rate
+┌──────────────────────────────────────────────────────────────┐
+│  Before: 0.02%  │  After: 0.02%  │  Change: +0.00%  │  ✅    │
+└──────────────────────────────────────────────────────────────┘
+
+## New Errors (Sentry)
+✅ No new errors detected in affected components
+
+## Performance (Web Vitals)
+| Metric | Before | After | Change | Status |
+|--------|--------|-------|--------|--------|
+| LCP | 2.1s | 2.1s | +0.00s | ✅ |
+| FID | 45ms | 44ms | -1ms | ✅ |
+| CLS | 0.05 | 0.05 | +0.00 | ✅ |
+
+## Bundle Size
+| Chunk | Before | After | Change | Status |
+|-------|--------|-------|--------|--------|
+| rent-checkout | 245KB | 246KB | +0.4% | ✅ |
+| business-modules | 128KB | 128KB | +0.0% | ✅ |
+
+## Feature Flags (Statsig)
+| Flag | Status | Rollout | Exposures |
+|------|--------|---------|-----------|
+| rent_frictionless_checkout_v2 | ✅ Active | 100% | 12,340 |
+
+## API Health
+| Endpoint | p50 | p95 | 5xx Rate |
+|----------|-----|-----|----------|
+| /booking/v2 | 120ms | 350ms | 0.01% |
+
+════════════════════════════════════════════════════════════════
+  VERDICT: ✅ HEALTHY
+════════════════════════════════════════════════════════════════
+
+All metrics within acceptable thresholds.
+Feature deployed successfully with no regressions.
+
+Recommended: Continue monitoring for 24h before closing ticket.
+```
+
+## Commands Used
+
+```bash
+# Get deployment info from GitHub
+gh api repos/YourCompany/com.yourcompany.web.public/deployments \
+  --jq '.[] | select(.environment == "production") | {sha, created_at}'
+
+# Check Sentry for new issues (requires SENTRY_API_TOKEN)
+curl -H "Authorization: Bearer $SENTRY_API_TOKEN" \
+  "https://sentry.io/api/0/projects/yourcompany/web-public/issues/?query=firstSeen:>=$DEPLOY_TIME"
+
+# Check bundle size from CI artifacts
+gh run view {RUN_ID} --json jobs \
+  --jq '.jobs[] | select(.name == "bundle-analysis") | .steps[].outputs'
+
+# Check Statsig feature status
+curl -H "STATSIG-API-KEY: $STATSIG_KEY" \
+  "https://statsigapi.net/console/v1/gates/rent_frictionless_checkout_v2"
+```
+
+## Alerting Rules
+
+| Condition                  | Action                      |
+| -------------------------- | --------------------------- |
+| Error rate > 0.5% increase | 🔴 Alert + suggest rollback |
+| LCP regression > 500ms     | 🟠 Warning + investigate    |
+| New Sentry errors > 10     | 🟠 Warning + triage         |
+| Bundle size > 10% increase | 🟡 Note for review          |
+| Feature flag disabled      | 🔴 Alert + investigate      |
+
+## AI Execution
+
+When user runs `/post-deploy-check {TICKET_ID}`:
+
+1. **Map ticket to deployment** - Find commit SHA from PR
+2. **Identify baseline** - Metrics before deployment
+3. **Collect current metrics** - Query monitoring tools
+4. **Compare and analyze** - Calculate deltas
+5. **Generate report** - Health status with recommendations
+6. **Alert if needed** - Trigger rollback suggestion if critical

package/commands/git/auto-rebase.md

@@ -0,0 +1,220 @@
+---
+description: Automatically rebase branch, detect and resolve conflicts with master
+category: PR Management
+aliases: [rebase, sync, update-branch]
+---
+
+# Auto-Rebase - Keep PRs Up to Date
+
+Automatically detect and resolve conflicts with master.
+
+## Usage
+
+```
+/auto-rebase
+/auto-rebase {PR_NUMBER}
+/auto-rebase --check-only
+```
+
+## What This Does
+
+1. **Detects** when your branch is behind master
+2. **Attempts** automatic rebase
+3. **Flags** conflicts for manual resolution
+4. **Re-runs** CI after successful rebase
+
+## Automatic Detection
+
+When running `/full-flow` or `/pr-fix`, I check:
+
+```bash
+# Check if behind master
+git fetch origin
+BEHIND=$(git rev-list --count HEAD..origin/master)
+
+if [ $BEHIND -gt 0 ]; then
+  echo "Branch is $BEHIND commits behind master"
+fi
+```
+
+### Detection Output
+
+```
+════════════════════════════════════════════════════════════════
+  ⚠️ BRANCH BEHIND MASTER
+════════════════════════════════════════════════════════════════
+
+Your branch: TICKET-123-display-name-charges
+Behind master by: 12 commits
+
+Recent master commits:
+  - abc1234: feat(TICKET-321): Add connector profile
+  - def5678: fix(TICKET-456): Fix tooltip positioning
+  - ghi9012: chore: Update dependencies
+
+Potential conflicts detected in:
+  ❌ src/features/checkout/src/components/PackagesV2.tsx
+  ✅ src/components/src/ProtectionPackageCard.tsx (clean)
+
+Options:
+  1. Auto-rebase (attempt automatic merge)
+  2. Manual rebase (I'll guide you)
+  3. Skip (continue with conflicts)
+
+Choose: (1/2/3)
+```
+
+## Auto-Rebase Flow
+
+### Step 1: Stash Local Changes
+
+```bash
+git stash push -m "auto-rebase-$(date +%s)"
+```
+
+### Step 2: Attempt Rebase
+
+```bash
+git fetch origin master
+git rebase origin/master
+```
+
+### Step 3: Handle Results
+
+**If clean rebase:**
+
+```
+✅ Rebase successful!
+   - Rebased 3 commits onto latest master
+   - No conflicts detected
+   - Pushing to origin...
+
+git push --force-with-lease origin HEAD
+```
+
+**If conflicts:**
+
+```
+════════════════════════════════════════════════════════════════
+  ⚠️ CONFLICTS DETECTED
+════════════════════════════════════════════════════════════════
+
+Conflicts in 2 files:
+
+1. src/features/checkout/src/components/PackagesV2.tsx
+   Lines 45-67: Both branches modified getLineItems()
+
+2. src/features/checkout/src/types/index.ts
+   Lines 12-15: Type definition changed
+
+Options:
+  A) Show me the conflicts (I'll help resolve)
+  B) Abort rebase, keep original state
+  C) Open in VS Code merge tool
+
+Choose: (a/b/c)
+```
+
+### Step 4: Resolve Conflicts (If Needed)
+
+```
+════════════════════════════════════════════════════════════════
+  CONFLICT: PackagesV2.tsx (lines 45-67)
+════════════════════════════════════════════════════════════════
+
+<<<<<<< HEAD (your changes)
+const lineItems = getModifiedLineItems(
+    rawLineItems,
+    false,
+    rent_frictionless_checkout_v2,
+    countryAlpha2
+);
+=======
+const lineItems = rawLineItems.map(item => ({
+    ...item,
+    displayName: item.display_name || item.name
+}));
+>>>>>>> origin/master
+
+Analysis:
+- Your version: Uses helper function (cleaner)
+- Master version: Inline mapping (simpler but duplicative)
+
+Recommendation: Keep YOUR version (helper function)
+Reason: Follows DRY principle, helper already handles edge cases
+
+Apply recommendation? (y/n)
+```
+
+### Step 5: Complete & Push
+
+```bash
+# After conflicts resolved
+git add -A
+git rebase --continue
+git push --force-with-lease origin HEAD
+```
+
+## CI Re-run
+
+After successful rebase:
+
+```
+✅ Rebase complete
+✅ Pushed to origin
+
+CI Status:
+  ⏳ Waiting for CI to start...
+  🔄 Running: lint, test, build
+
+I'll notify you when CI completes.
+```
+
+## Commands Reference
+
+```bash
+# Check rebase status
+git status
+
+# View conflicts
+git diff --name-only --diff-filter=U
+
+# Abort if needed
+git rebase --abort
+
+# Force push after rebase
+git push --force-with-lease origin HEAD
+```
+
+## Safety Features
+
+1. **Stash before rebase** - Never lose local changes
+2. **force-with-lease** - Prevents overwriting others' work
+3. **Conflict preview** - Shows what will conflict before attempting
+4. **Easy abort** - Can always return to original state
+
+## Integration with /full-flow
+
+During state detection:
+
+```
+════════════════════════════════════════════════════════════════
+  STATE DETECTION
+════════════════════════════════════════════════════════════════
+
+  Branch:        ✅ TICKET-123-display-name-charges
+  Commits:       ✅ 3 commits ahead
+  Behind Master: ⚠️ 12 commits behind
+  PR:            ✅ #23043 (draft)
+
+⚠️ Your branch is behind master. Rebase recommended before continuing.
+
+Auto-rebase now? (y/n)
+```
+
+## Best Practices
+
+1. **Rebase frequently** - Don't let branch drift too far
+2. **Rebase before review** - Fresh code is easier to review
+3. **Rebase after review** - Incorporate latest changes before merge
+4. **Never rebase shared branches** - Only your feature branches