proagents 1.0.0

package/proagents/git/pr-workflow.md

@@ -0,0 +1,286 @@
+# Pull Request Workflow
+
+Standard workflow for creating and reviewing pull requests.
+
+---
+
+## Creating a Pull Request
+
+### Step 1: Prepare Branch
+
+```bash
+# Ensure branch is up to date
+git fetch origin
+git rebase origin/develop
+
+# Push branch
+git push origin feature/my-feature -u
+```
+
+### Step 2: Create PR
+
+Using GitHub CLI:
+```bash
+gh pr create --title "feat(scope): description" --body "$(cat <<'EOF'
+## Summary
+Brief description of changes.
+
+## Changes
+- Change 1
+- Change 2
+
+## Test Plan
+- [ ] Unit tests added
+- [ ] Manual testing completed
+
+## Screenshots
+(if applicable)
+
+---
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+EOF
+)"
+```
+
+---
+
+## PR Title Format
+
+Follow commit conventions:
+```
+<type>(<scope>): <description>
+
+Examples:
+feat(auth): add password reset flow
+fix(api): handle null response in user service
+docs(readme): update installation instructions
+```
+
+---
+
+## PR Description Template
+
+```markdown
+## Summary
+[Brief description of what this PR does]
+
+## Related Issue
+Fixes #[issue number]
+
+## Changes
+- [Change 1]
+- [Change 2]
+- [Change 3]
+
+## Type of Change
+- [ ] Bug fix (non-breaking change that fixes an issue)
+- [ ] New feature (non-breaking change that adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation update
+
+## Test Plan
+- [ ] Unit tests added/updated
+- [ ] Integration tests added/updated
+- [ ] Manual testing completed
+
+## Screenshots
+[If applicable, add screenshots]
+
+## Checklist
+- [ ] Code follows project conventions
+- [ ] Self-review completed
+- [ ] Documentation updated
+- [ ] Tests pass locally
+- [ ] No new warnings
+
+## Notes for Reviewers
+[Any additional context for reviewers]
+```
+
+---
+
+## Review Process
+
+### For Authors
+
+1. **Self-Review First**
+   - Review your own diff
+   - Check for obvious issues
+   - Ensure tests pass
+
+2. **Request Reviews**
+   - Add appropriate reviewers
+   - CODEOWNERS auto-assigns owners
+
+3. **Respond to Feedback**
+   - Address all comments
+   - Explain decisions if disagreeing
+   - Mark resolved when addressed
+
+4. **Keep Updated**
+   - Rebase if base branch updated
+   - Resolve merge conflicts promptly
+
+### For Reviewers
+
+1. **Timely Review**
+   - Review within SLA (see code-ownership.md)
+   - Don't let PRs go stale
+
+2. **Review Checklist**
+   - Code correctness
+   - Code style
+   - Test coverage
+   - Documentation
+   - Security
+   - Performance
+
+3. **Provide Constructive Feedback**
+   - Be specific
+   - Explain why
+   - Suggest alternatives
+   - Distinguish blocking vs non-blocking
+
+4. **Approve or Request Changes**
+   - Approve if ready
+   - Request changes with clear items
+   - Comment if just suggestions
+
+---
+
+## Review Comment Conventions
+
+### Blocking (Must Fix)
+```
+🔴 **Blocking:** This could cause [issue].
+Suggested fix: [suggestion]
+```
+
+### Should Fix (Important)
+```
+🟡 **Important:** Consider [change].
+Reason: [explanation]
+```
+
+### Suggestion (Optional)
+```
+💡 **Suggestion:** You might want to [improvement].
+```
+
+### Question
+```
+❓ **Question:** Why did you choose [approach]?
+```
+
+### Praise
+```
+✅ **Nice!** This is a clean solution.
+```
+
+---
+
+## Merge Requirements
+
+### Required Checks
+- [ ] CI passes (tests, lint, build)
+- [ ] Required reviewers approved
+- [ ] No merge conflicts
+- [ ] Branch up to date
+
+### Merge Strategies
+
+**Squash and Merge (Recommended)**
+- For feature branches
+- Creates clean history
+- Single commit per feature
+
+**Rebase and Merge**
+- For clean commit history
+- Preserves individual commits
+- Use when commits are atomic
+
+**Merge Commit**
+- For long-running branches
+- Preserves full history
+- Shows merge point
+
+---
+
+## After Merge
+
+1. **Delete Branch**
+   ```bash
+   git branch -d feature/my-feature
+   git push origin --delete feature/my-feature
+   ```
+
+2. **Update Local**
+   ```bash
+   git checkout develop
+   git pull origin develop
+   ```
+
+3. **Verify Deployment**
+   - Check CI/CD pipeline
+   - Verify staging deployment
+   - Monitor for issues
+
+---
+
+## Handling Feedback
+
+### If Changes Requested
+
+```bash
+# Make changes
+git add .
+git commit -m "address review feedback"
+git push origin feature/my-feature
+
+# Or amend if single change
+git add .
+git commit --amend
+git push --force-with-lease
+```
+
+### If Conflicts Arise
+
+```bash
+# Update from base
+git fetch origin
+git rebase origin/develop
+
+# Resolve conflicts
+# ... resolve in editor ...
+
+git add .
+git rebase --continue
+git push --force-with-lease
+```
+
+---
+
+## PR Size Guidelines
+
+| Size | Lines Changed | Review Time |
+|------|---------------|-------------|
+| Small | < 100 | < 30 min |
+| Medium | 100-500 | 1-2 hours |
+| Large | > 500 | Consider splitting |
+
+### Tips for Smaller PRs
+- Break features into increments
+- Separate refactoring from features
+- Use feature flags for partial work
+- Create dependent PRs
+
+---
+
+## Slash Commands
+
+| Command | Description |
+|---------|-------------|
+| `/pr-create` | Create pull request |
+| `/pr-update` | Update PR description |
+| `/pr-merge` | Merge pull request |
+| `/pr-review` | Request review |

package/proagents/git/rollback-procedures.md

@@ -0,0 +1,416 @@
+# Git Rollback Procedures
+
+Safe and effective rollback strategies using Git.
+
+---
+
+## Overview
+
+This guide covers rollback procedures for:
+- Code rollbacks
+- Release rollbacks
+- Emergency hotfixes
+- Database-coordinated rollbacks
+
+---
+
+## Rollback Types
+
+### 1. Quick Rollback (Last Commit)
+
+**When:** Single bad commit needs reverting
+
+```bash
+# Revert the last commit (creates new commit)
+git revert HEAD
+
+# Revert without auto-commit (review first)
+git revert HEAD --no-commit
+git diff --staged  # Review changes
+git commit -m "Revert: [original commit message]"
+```
+
+**Best for:** Small changes, bug fixes gone wrong
+
+---
+
+### 2. Feature Rollback (Multiple Commits)
+
+**When:** Entire feature needs reverting
+
+```bash
+# Find where feature started
+git log --oneline --graph
+
+# Revert range of commits (oldest to newest)
+git revert --no-commit abc123..def456
+git commit -m "Revert: feature-name due to [reason]"
+
+# OR revert a merge commit
+git revert -m 1 <merge-commit-hash>
+```
+
+**Example:**
+```bash
+# Feature was merged in commit abc123
+git revert -m 1 abc123
+
+# Message
+Revert: Merge feature/user-auth
+
+Reason: Authentication causing 500 errors in production
+Ticket: ISSUE-456
+```
+
+---
+
+### 3. Release Rollback (Version Tag)
+
+**When:** Entire release needs reverting
+
+```bash
+# Current: v1.2.0 (broken)
+# Target: v1.1.0 (last stable)
+
+# Option A: Reset to previous tag (CAREFUL - destructive)
+git reset --hard v1.1.0
+git push --force origin main  # Requires permissions
+
+# Option B: Revert all commits since last release (safe)
+git revert --no-commit v1.1.0..v1.2.0
+git commit -m "Revert: v1.2.0 release - rolling back to v1.1.0"
+git tag v1.2.1
+git push origin main --tags
+```
+
+**Best for:** Major release issues
+
+---
+
+### 4. Emergency Hotfix
+
+**When:** Critical fix needed immediately
+
+```bash
+# Start from production tag
+git checkout v1.2.0
+git checkout -b hotfix/critical-fix
+
+# Make minimal fix
+# ... edit files ...
+
+git add .
+git commit -m "hotfix: Critical fix for [issue]"
+
+# Create new tag
+git tag v1.2.1
+
+# Merge back to main
+git checkout main
+git merge hotfix/critical-fix
+
+# Push everything
+git push origin main --tags
+```
+
+---
+
+## Rollback Decision Tree
+
+```
+Problem Detected
+       │
+       ▼
+┌──────────────────┐
+│ Can quick fix?   │──Yes──▶ Deploy hotfix
+└──────────────────┘
+       │ No
+       ▼
+┌──────────────────┐
+│ Single commit?   │──Yes──▶ git revert HEAD
+└──────────────────┘
+       │ No
+       ▼
+┌──────────────────┐
+│ Feature merge?   │──Yes──▶ git revert -m 1 <merge>
+└──────────────────┘
+       │ No
+       ▼
+┌──────────────────┐
+│ Multiple commits │──Yes──▶ git revert <range>
+└──────────────────┘
+       │ No
+       ▼
+┌──────────────────┐
+│ Full release?    │──Yes──▶ Revert to previous tag
+└──────────────────┘
+```
+
+---
+
+## Rollback Checklist
+
+### Before Rollback
+```markdown
+- [ ] Confirm the issue requires rollback (not fixable quickly)
+- [ ] Identify exact commits/release to roll back
+- [ ] Notify stakeholders (team, support, customers if needed)
+- [ ] Check for database migrations that need reverting
+- [ ] Prepare rollback script/commands
+- [ ] Ensure access to deployment pipeline
+```
+
+### During Rollback
+```markdown
+- [ ] Put application in maintenance mode (if applicable)
+- [ ] Execute Git rollback commands
+- [ ] Revert any database migrations
+- [ ] Deploy rolled-back code
+- [ ] Verify application health checks
+- [ ] Test critical paths manually
+```
+
+### After Rollback
+```markdown
+- [ ] Monitor error rates and performance
+- [ ] Communicate completion to stakeholders
+- [ ] Create incident report
+- [ ] Schedule post-mortem
+- [ ] Plan proper fix for original issue
+```
+
+---
+
+## Database-Coordinated Rollback
+
+When rollback involves database changes:
+
+```bash
+# 1. Put app in maintenance mode
+./scripts/maintenance-mode on
+
+# 2. Run database rollback
+npm run db:migrate:down
+# OR
+npx prisma migrate reset --to <migration-name>
+
+# 3. Verify database state
+npm run db:verify
+
+# 4. Git rollback
+git revert <commits>
+
+# 5. Deploy rolled-back code
+./scripts/deploy
+
+# 6. Exit maintenance mode
+./scripts/maintenance-mode off
+
+# 7. Verify application
+curl -f https://api.example.com/health
+```
+
+---
+
+## Rollback Scripts
+
+### Automated Rollback Script
+
+```bash
+#!/bin/bash
+# rollback.sh
+
+set -e
+
+# Configuration
+ROLLBACK_TARGET="${1:-HEAD~1}"
+ENVIRONMENT="${2:-staging}"
+
+echo "=== Starting Rollback ==="
+echo "Target: $ROLLBACK_TARGET"
+echo "Environment: $ENVIRONMENT"
+
+# Confirm
+read -p "Continue? (y/n) " -n 1 -r
+echo
+if [[ ! $REPLY =~ ^[Yy]$ ]]; then
+    exit 1
+fi
+
+# Create rollback branch
+BRANCH="rollback/$(date +%Y%m%d-%H%M%S)"
+git checkout -b "$BRANCH"
+
+# Perform rollback
+if [[ "$ROLLBACK_TARGET" == v* ]]; then
+    # Tag-based rollback
+    CURRENT_TAG=$(git describe --tags --abbrev=0)
+    git revert --no-commit "$ROLLBACK_TARGET..$CURRENT_TAG"
+else
+    # Commit-based rollback
+    git revert --no-commit "$ROLLBACK_TARGET"
+fi
+
+# Commit rollback
+git commit -m "Rollback to $ROLLBACK_TARGET
+
+Environment: $ENVIRONMENT
+Reason: Emergency rollback
+Date: $(date)
+"
+
+# Push
+git push origin "$BRANCH"
+
+# Create PR (using GitHub CLI)
+gh pr create \
+    --title "ROLLBACK: Revert to $ROLLBACK_TARGET" \
+    --body "## Emergency Rollback
+
+Target: $ROLLBACK_TARGET
+Environment: $ENVIRONMENT
+Time: $(date)
+
+### Checklist
+- [ ] Database rollback completed (if applicable)
+- [ ] Smoke tests passed
+- [ ] Stakeholders notified
+" \
+    --label "rollback,urgent"
+
+echo "=== Rollback PR Created ==="
+echo "Please review and merge to deploy"
+```
+
+---
+
+## Recovery Scenarios
+
+### Scenario 1: Accidental Force Push
+
+```bash
+# Find the previous HEAD in reflog
+git reflog show origin/main
+
+# Output:
+# abc1234 origin/main@{0}: update by push --force
+# xyz5678 origin/main@{1}: update by push  <-- This is what we want
+
+# Restore
+git checkout main
+git reset --hard xyz5678
+git push --force origin main
+
+# Notify team
+echo "Main branch restored to xyz5678. Please re-pull."
+```
+
+### Scenario 2: Merged Wrong Branch
+
+```bash
+# Revert the merge commit
+git revert -m 1 <merge-commit-hash>
+
+# Push the revert
+git push origin main
+
+# Note: If you need to re-merge later
+git checkout feature-branch
+git revert <revert-commit-hash>  # Undo the revert
+git checkout main
+git merge feature-branch
+```
+
+### Scenario 3: Lost Commits
+
+```bash
+# Check reflog for lost commits
+git reflog
+
+# Find the commit
+git show abc1234
+
+# Recover it
+git cherry-pick abc1234
+
+# Or create branch from it
+git checkout -b recovered-commits abc1234
+```
+
+---
+
+## Rollback Communication Template
+
+```markdown
+## Rollback Notification
+
+**Status:** 🔄 Rollback In Progress / ✅ Rollback Complete
+
+**Time:** [UTC timestamp]
+**Environment:** [Production/Staging]
+**Duration:** [Expected/Actual duration]
+
+### What Happened
+[Brief description of the issue that caused rollback]
+
+### Impact
+- [Affected features/services]
+- [User impact description]
+
+### Actions Taken
+1. [Action 1]
+2. [Action 2]
+3. [Action 3]
+
+### Current Status
+- Application: [Healthy/Degraded/Down]
+- Error rate: [X%]
+- Response time: [Xms]
+
+### Next Steps
+- [ ] Complete root cause analysis
+- [ ] Schedule fix implementation
+- [ ] Post-mortem meeting
+
+### Contact
+[On-call engineer name/contact]
+```
+
+---
+
+## Configuration
+
+```yaml
+# proagents.config.yaml
+
+git:
+  rollback:
+    auto_create_backup_branch: true
+    require_confirmation: true
+    notify_on_rollback: true
+
+    notifications:
+      slack_channel: "#deployments"
+      email: ["oncall@company.com"]
+
+    protection:
+      require_approval_for_production: true
+      max_commits_without_confirmation: 5
+
+    scripts:
+      pre_rollback: "./scripts/pre-rollback.sh"
+      post_rollback: "./scripts/post-rollback.sh"
+```
+
+---
+
+## Slash Commands
+
+| Command | Description |
+|---------|-------------|
+| `/rollback` | Start rollback wizard |
+| `/rollback --last` | Revert last commit |
+| `/rollback --to [tag]` | Rollback to specific tag |
+| `/rollback --commits [n]` | Revert last n commits |
+| `/rollback --dry-run` | Preview rollback changes |
+| `/rollback --status` | Check current rollback status |