proagents 1.6.20 → 1.6.22

package/.proagents/git/commit-conventions.md

@@ -1,241 +0,0 @@
-# Git Commit Conventions
-
-Standard commit message format for ProAgents projects.
-
----
-
-## Conventional Commits
-
-Format:
-```
-<type>(<scope>): <description>
-
-[optional body]
-
-[optional footer(s)]
-```
-
----
-
-## Commit Types
-
-| Type | Description | Example |
-|------|-------------|---------|
-| `feat` | New feature | `feat(auth): add login form` |
-| `fix` | Bug fix | `fix(api): handle null response` |
-| `docs` | Documentation | `docs(readme): update install steps` |
-| `style` | Formatting (no code change) | `style: format with prettier` |
-| `refactor` | Code change (no new feature/fix) | `refactor(user): simplify validation` |
-| `perf` | Performance improvement | `perf(list): virtualize long lists` |
-| `test` | Adding tests | `test(auth): add login tests` |
-| `build` | Build system changes | `build: update webpack config` |
-| `ci` | CI configuration | `ci: add github actions` |
-| `chore` | Maintenance tasks | `chore: update dependencies` |
-| `revert` | Revert previous commit | `revert: revert "feat(auth)..."` |
-
----
-
-## Scope
-
-Scope indicates the affected area:
-- Feature name: `auth`, `users`, `payments`
-- Component: `button`, `modal`, `form`
-- Module: `api`, `store`, `utils`
-
-```
-feat(auth): add password reset
-fix(button): fix hover state
-refactor(api): extract common headers
-```
-
----
-
-## Description
-
-- Use imperative mood: "add" not "added"
-- Don't capitalize first letter
-- No period at the end
-- Keep under 50 characters
-
-```
-✅ Good:
-feat(auth): add login form validation
-fix(api): handle timeout errors
-docs: update contributing guide
-
-❌ Bad:
-feat(auth): Added login form validation.  (past tense, period)
-fix: Fix bug                              (not descriptive)
-FEAT: Add feature                         (caps)
-```
-
----
-
-## Body
-
-Use for additional context:
-- What changes were made
-- Why the change was necessary
-- Any implications
-
-```
-feat(cart): add quantity limit
-
-Add maximum quantity limit of 99 items per product
-to prevent inventory issues and improve UX.
-
-Previously users could add unlimited quantities
-which caused checkout failures.
-```
-
----
-
-## Footer
-
-### Breaking Changes
-
-```
-feat(api): change response format
-
-BREAKING CHANGE: API now returns data wrapped in `data` field.
-Previously: { id, name }
-Now: { data: { id, name } }
-```
-
-### Issue References
-
-```
-fix(login): prevent double submission
-
-Fixes #123
-Closes #456
-Related to #789
-```
-
-### Co-authors
-
-```
-feat(dashboard): add analytics widget
-
-Co-authored-by: Name <email@example.com>
-Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
-```
-
----
-
-## Examples
-
-### Simple Commit
-```
-feat(auth): add password strength indicator
-```
-
-### Commit with Body
-```
-fix(api): handle network timeout gracefully
-
-Previously, network timeouts would cause the app to crash.
-Now we catch timeout errors and show a user-friendly message
-with a retry option.
-```
-
-### Breaking Change
-```
-refactor(api)!: update authentication endpoint
-
-BREAKING CHANGE: Auth endpoint moved from /auth to /api/v2/auth.
-Update all client configurations to use new endpoint.
-
-Migration guide: docs/migration/auth-v2.md
-```
-
-### Full Commit
-```
-feat(payments): add stripe integration
-
-Implement Stripe payment processing for checkout flow:
-- Add Stripe SDK integration
-- Create payment intent on server
-- Handle payment confirmation
-- Add webhook for payment events
-
-Requires STRIPE_SECRET_KEY environment variable.
-
-Closes #234
-Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
-```
-
----
-
-## Commit Size
-
-### Good Commits
-- Single logical change
-- Can be reverted independently
-- Tests pass at each commit
-- Clear purpose
-
-### Avoid
-- Multiple unrelated changes
-- "WIP" commits in main branch
-- Broken intermediate states
-- Huge commits (> 500 lines)
-
----
-
-## Commit Message Template
-
-Create `.gitmessage`:
-```
-# <type>(<scope>): <description>
-#
-# Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore
-#
-# Body: Explain what and why (not how)
-#
-# Footer: Breaking changes, issue references, co-authors
-```
-
-Configure git:
-```bash
-git config --global commit.template ~/.gitmessage
-```
-
----
-
-## Automation
-
-### commitlint
-
-```javascript
-// commitlint.config.js
-module.exports = {
-  extends: ['@commitlint/config-conventional'],
-  rules: {
-    'type-enum': [2, 'always', [
-      'feat', 'fix', 'docs', 'style', 'refactor',
-      'perf', 'test', 'build', 'ci', 'chore', 'revert'
-    ]],
-    'scope-case': [2, 'always', 'kebab-case'],
-    'subject-case': [2, 'always', 'lower-case'],
-    'subject-max-length': [2, 'always', 72],
-  },
-};
-```
-
-### Husky Pre-commit
-
-```bash
-npx husky add .husky/commit-msg 'npx commitlint --edit $1'
-```
-
----
-
-## Commands
-
-| Command | Description |
-|---------|-------------|
-| `pa:commit-feat` | Create feature commit |
-| `pa:commit-fix` | Create fix commit |
-| `pa:commit-docs` | Create docs commit |
-| `pa:commit-refactor` | Create refactor commit |

package/.proagents/git/pr-workflow.md

@@ -1,286 +0,0 @@
-# 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
-
----
-
-## Commands
-
-| Command | Description |
-|---------|-------------|
-| `pa:pr-create` | Create pull request |
-| `pa:pr-update` | Update PR description |
-| `pa:pr-merge` | Merge pull request |
-| `pa:pr-review` | Request review |