aidevops 2.52.1

package/.agent/tools/deployment/vercel.md

@@ -0,0 +1,390 @@
+---
+description: Vercel CLI for serverless deployment
+mode: subagent
+tools:
+  read: true
+  write: false
+  edit: false
+  bash: true
+  glob: true
+  grep: true
+  webfetch: true
+  task: true
+---
+
+# Vercel CLI Integration
+
+<!-- AI-CONTEXT-START -->
+
+## Quick Reference
+
+- **CLI**: `vercel` (install: `npm i -g vercel`)
+- **Auth**: `vercel login` → `vercel whoami`
+- **Config**: `configs/vercel-cli-config.json`
+- **Script**: `.agent/scripts/vercel-cli-helper.sh`
+- **Local Dev First**: Works without auth for immediate development
+
+**Commands**: `list-projects|deploy|get-project|list-deployments|list-env|add-env|remove-env|list-domains|add-domain|list-accounts|whoami|dev|build`
+
+**Usage**: `./.agent/scripts/vercel-cli-helper.sh [command] [account] [args]`
+
+**Environments**: development, preview, production
+**Frameworks**: Next.js, React, Vue, Nuxt, Svelte, Angular, static sites
+
+**Local Dev** (no auth): `./.agent/scripts/vercel-cli-helper.sh dev personal ./app 3000`
+<!-- AI-CONTEXT-END -->
+
+Comprehensive Vercel deployment and project management using the Vercel CLI through the AI DevOps Framework.
+
+## Overview
+
+The Vercel CLI helper provides complete automation for:
+
+- **Local Development**: Works without authentication for immediate setup
+- Project deployment and management
+- Environment variable configuration
+- Domain management and SSL setup
+- Team and account management
+- Deployment monitoring and rollbacks
+
+### 🚀 **Local Development First**
+
+The integration is designed to work **immediately** for local development without requiring Vercel authentication:
+
+- **Node.js Projects**: Automatically detects and runs `npm run dev` or `npm run start`
+- **Static HTML**: Serves static files using Python HTTP server
+- **Next.js/React**: Full framework support with hot reloading
+- **Universal Build**: Runs local build scripts without cloud dependencies
+
+## Prerequisites
+
+### Install Vercel CLI
+
+```bash
+# Using npm
+npm i -g vercel
+
+# Using yarn
+yarn global add vercel
+
+# Using pnpm
+pnpm add -g vercel
+```
+
+### Authentication
+
+```bash
+# Login to Vercel
+vercel login
+
+# Verify authentication
+vercel whoami
+```
+
+### Dependencies
+
+- **Vercel CLI**: Latest version
+- **jq**: JSON processor for configuration management
+- **Node.js**: Version 16+ recommended
+
+## Configuration
+
+### Setup Configuration File
+
+```bash
+# Copy template
+cp configs/vercel-cli-config.json.txt configs/vercel-cli-config.json
+
+# Edit configuration
+nano configs/vercel-cli-config.json
+```
+
+### Configuration Structure
+
+```json
+{
+  "accounts": {
+    "personal": {
+      "team_name": "Personal",
+      "team_id": "",
+      "description": "Personal account",
+      "default_environment": "preview"
+    },
+    "company": {
+      "team_name": "Company Name",
+      "team_id": "team_abc123",
+      "description": "Company team account",
+      "default_environment": "preview"
+    }
+  },
+  "projects": {
+    "my-app": {
+      "account": "personal",
+      "framework": "nextjs",
+      "domains": ["example.com"]
+    }
+  }
+}
+```
+
+## Usage Examples
+
+### Project Management
+
+```bash
+# List all projects
+./.agent/scripts/vercel-cli-helper.sh list-projects personal
+
+# Deploy to preview environment
+./.agent/scripts/vercel-cli-helper.sh deploy personal ./my-app preview
+
+# Deploy to production
+./.agent/scripts/vercel-cli-helper.sh deploy personal ./my-app production
+
+# Get project information
+./.agent/scripts/vercel-cli-helper.sh get-project personal my-app
+
+# List recent deployments
+./.agent/scripts/vercel-cli-helper.sh list-deployments personal my-app 10
+```
+
+### Environment Variables
+
+```bash
+# List environment variables
+./.agent/scripts/vercel-cli-helper.sh list-env personal my-app development
+
+# Add environment variable
+./.agent/scripts/vercel-cli-helper.sh add-env personal my-app API_KEY "secret-value" production
+
+# Remove environment variable
+./.agent/scripts/vercel-cli-helper.sh remove-env personal my-app OLD_VAR production
+```
+
+### Domain Management
+
+```bash
+# List domains
+./.agent/scripts/vercel-cli-helper.sh list-domains personal
+
+# Add domain to project
+./.agent/scripts/vercel-cli-helper.sh add-domain personal my-app example.com
+```
+
+### Account Management
+
+```bash
+# List configured accounts
+./.agent/scripts/vercel-cli-helper.sh list-accounts
+
+# Show current Vercel user
+./.agent/scripts/vercel-cli-helper.sh whoami
+```
+
+## Advanced Features
+
+### Team Management
+
+For team accounts, configure the `team_id` in your account configuration:
+
+```json
+{
+  "accounts": {
+    "company": {
+      "team_name": "My Company",
+      "team_id": "team_abc123def456",
+      "description": "Company Vercel team"
+    }
+  }
+}
+```
+
+### Custom Build Configuration
+
+Configure project-specific build settings:
+
+```json
+{
+  "projects": {
+    "my-app": {
+      "build_command": "npm run build",
+      "output_directory": "dist",
+      "install_command": "npm ci",
+      "node_version": "18.x"
+    }
+  }
+}
+```
+
+### Local Development (No Authentication Required)
+
+Perfect for immediate development without any setup:
+
+```bash
+# Start development server (works immediately)
+./.agent/scripts/vercel-cli-helper.sh dev personal ./my-app 3000
+
+# Build project locally
+./.agent/scripts/vercel-cli-helper.sh build personal ./my-app
+
+# Works with any project type:
+# - Node.js projects with package.json
+# - Static HTML files
+# - Next.js, React, Vue, Svelte
+# - Any framework with npm scripts
+```
+
+### Multiple Environments
+
+Support for development, preview, and production environments:
+
+```bash
+# Local development (no auth required)
+./.agent/scripts/vercel-cli-helper.sh dev personal ./app 3000
+
+# Deploy to specific environments (requires auth)
+./.agent/scripts/vercel-cli-helper.sh deploy personal ./app development
+./.agent/scripts/vercel-cli-helper.sh deploy personal ./app preview
+./.agent/scripts/vercel-cli-helper.sh deploy personal ./app production
+```
+
+## Integration with CI/CD
+
+### GitHub Actions Integration
+
+```yaml
+name: Deploy to Vercel
+on:
+  push:
+    branches: [main]
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Deploy to Vercel
+        run: |
+          ./.agent/scripts/vercel-cli-helper.sh deploy production ./ production
+        env:
+          VERCEL_TOKEN: ${{ secrets.VERCEL_TOKEN }}
+```
+
+### Environment-Specific Deployments
+
+```bash
+# Preview deployments for feature branches
+./.agent/scripts/vercel-cli-helper.sh deploy personal ./app preview
+
+# Production deployments for main branch
+./.agent/scripts/vercel-cli-helper.sh deploy personal ./app production
+```
+
+## Security Best Practices
+
+### Token Management
+
+- Store Vercel tokens securely in environment variables
+- Use team-scoped tokens for organization projects
+- Rotate tokens regularly
+
+### Environment Variables
+
+- Use different values for development, preview, and production
+- Store sensitive values in Vercel's encrypted environment variables
+- Never commit secrets to version control
+
+### Domain Security
+
+- Enable HTTPS for all custom domains
+- Configure proper security headers
+- Use Vercel's DDoS protection features
+
+## Troubleshooting
+
+### Common Issues
+
+1. **Authentication Failed**
+
+   ```bash
+   vercel login
+   vercel whoami
+   ```
+
+2. **Team Access Issues**
+   - Verify team_id in configuration
+   - Check team membership permissions
+
+3. **Build Failures**
+   - Check build logs: `vercel logs [deployment-url]`
+   - Verify build command and output directory
+
+4. **Domain Configuration**
+   - Verify DNS settings
+   - Check domain ownership
+
+### Debug Mode
+
+Enable verbose logging:
+
+```bash
+# Set debug environment variable
+export DEBUG=1
+./.agent/scripts/vercel-cli-helper.sh deploy personal ./app
+```
+
+## Framework Support
+
+Vercel CLI helper supports all major frameworks:
+
+- **Next.js**: Full-stack React framework
+- **React**: Client-side React applications
+- **Vue.js**: Progressive JavaScript framework
+- **Nuxt.js**: Vue.js framework
+- **Svelte/SvelteKit**: Modern web framework
+- **Angular**: TypeScript-based framework
+- **Static Sites**: HTML, CSS, JavaScript
+
+## Performance Optimization
+
+### Build Optimization
+
+- Use appropriate Node.js version
+- Configure build caching
+- Optimize bundle size
+- Enable compression
+
+### Deployment Speed
+
+- Use incremental builds
+- Configure proper ignore patterns
+- Optimize asset delivery
+
+## Monitoring and Analytics
+
+### Built-in Analytics
+
+- Web Analytics for traffic insights
+- Speed Insights for performance monitoring
+- Real User Monitoring (RUM)
+
+### Custom Monitoring
+
+```bash
+# View deployment logs
+vercel logs [deployment-url]
+
+# Monitor function performance
+vercel inspect [deployment-url]
+```
+
+## API Integration
+
+The helper script integrates with Vercel's REST API for advanced operations:
+
+- Project management
+- Deployment automation
+- Team administration
+- Usage analytics
+
+For direct API access, see the [Vercel API documentation](https://vercel.com/docs/rest-api).

package/.agent/tools/git/authentication.md

@@ -0,0 +1,132 @@
+---
+description: Authentication setup for GitHub, GitLab, and Gitea
+mode: subagent
+tools:
+  read: true
+  write: false
+  edit: false
+  bash: true
+  glob: true
+  grep: true
+  webfetch: false
+  task: true
+---
+
+# Git Platform Authentication
+
+<!-- AI-CONTEXT-START -->
+
+## Quick Reference
+
+| Platform | Token Location | Required Scopes |
+|----------|---------------|-----------------|
+| GitHub | Settings → Developer settings → Personal access tokens | `repo`, `admin:repo_hook`, `user` |
+| GitLab | User Settings → Access Tokens | `api`, `read_repository`, `write_repository` |
+| Gitea | Settings → Applications | Full access |
+
+**Secure storage**: `~/.config/aidevops/` (600 permissions)
+**Never**: Store tokens in repository files
+
+<!-- AI-CONTEXT-END -->
+
+## GitHub Personal Access Token
+
+### Create Token
+
+1. Go to **Settings** → **Developer settings** → **Personal access tokens**
+2. Click **Generate new token (classic)**
+3. Select scopes:
+   - `repo` - Full control of private repositories
+   - `admin:repo_hook` - Read and write repository hooks
+   - `user` - Read user profile data
+4. Generate and copy token
+
+### Store Securely
+
+```bash
+# Using CLI (recommended)
+gh auth login
+
+# Or store for scripts
+echo "GITHUB_TOKEN=ghp_xxxx" >> ~/.config/aidevops/mcp-env.sh
+chmod 600 ~/.config/aidevops/mcp-env.sh
+```
+
+### Verify
+
+```bash
+gh auth status
+# or
+curl -H "Authorization: token $GITHUB_TOKEN" https://api.github.com/user
+```
+
+## GitLab Personal Access Token
+
+### Create Token
+
+1. Go to **User Settings** → **Access Tokens**
+2. Create personal access token with scopes:
+   - `api` - Access the authenticated user's API
+   - `read_repository` - Read repository
+   - `write_repository` - Write repository
+   - `read_user` - Read user info
+3. Copy token (shown only once)
+
+### Store Securely
+
+```bash
+# Using CLI (recommended)
+glab auth login
+
+# For self-hosted
+glab auth login --hostname gitlab.company.com
+
+# Or store for scripts
+echo "GITLAB_TOKEN=glpat-xxxx" >> ~/.config/aidevops/mcp-env.sh
+chmod 600 ~/.config/aidevops/mcp-env.sh
+```
+
+### Verify
+
+```bash
+glab auth status
+```
+
+## Gitea Access Token
+
+### Create Token
+
+1. Go to **Settings** → **Applications**
+2. Generate new access token
+3. Copy token (shown only once)
+
+### Store Securely
+
+```bash
+# Using CLI
+tea login add --name myserver --url https://git.example.com --token YOUR_TOKEN
+
+# Or store for scripts
+echo "GITEA_TOKEN=xxxx" >> ~/.config/aidevops/mcp-env.sh
+chmod 600 ~/.config/aidevops/mcp-env.sh
+```
+
+### Verify
+
+```bash
+tea login list
+```
+
+## Token Security Best Practices
+
+1. **Minimal scopes** - Only request permissions you need
+2. **Regular rotation** - Rotate tokens every 6-12 months
+3. **Secure storage** - Use `~/.config/aidevops/` with 600 permissions
+4. **Never in repos** - Never commit tokens to version control
+5. **Use CLI auth** - Prefer `gh auth login` over env vars when possible
+6. **Monitor usage** - Review API access logs periodically
+
+## Related
+
+- **CLI usage**: `tools/git.md`
+- **Security practices**: `git/security.md`

package/.agent/tools/git/gitea-cli.md

@@ -0,0 +1,193 @@
+---
+description: Gitea CLI (tea) for repos, PRs, and issues
+mode: subagent
+tools:
+  read: true
+  write: false
+  edit: false
+  bash: true
+  glob: true
+  grep: true
+  webfetch: true
+  task: true
+---
+
+# Gitea CLI Helper Documentation
+
+<!-- AI-CONTEXT-START -->
+
+## Quick Reference
+
+- **CLI Tool**: `tea` (Gitea CLI)
+- **Install**: `brew install tea` (macOS) | `go install code.gitea.io/tea/cmd/tea@latest`
+- **Auth**: `tea login add --name <name> --url <url> --token <token>`
+- **Config**: `configs/gitea-cli-config.json`
+- **Script**: `.agent/scripts/gitea-cli-helper.sh`
+- **Requires**: `jq` for JSON parsing
+
+**Commands**: `list-repos|create-repo|delete-repo|list-issues|create-issue|close-issue|list-prs|create-pr|merge-pr|list-branches|create-branch`
+
+**Usage**: `./providers/gitea-cli-helper.sh [command] [account] [args]`
+
+**Multi-Instance**: Account name in config MUST match `tea` login name
+**Note**: Token in JSON used for API calls tea doesn't support (e.g., branch creation)
+<!-- AI-CONTEXT-END -->
+
+## Overview
+
+The Gitea CLI Helper provides a comprehensive interface for managing Gitea repositories, issues, pull requests, and branches directly from the command line. It leverages the `tea` CLI tool and the Gitea API to offer a seamless experience for developers working with one or multiple Gitea instances.
+
+## Prerequisites
+
+1. **Gitea CLI (`tea`)**: Must be installed.
+    - **Homebrew (macOS/Linux)**: `brew install tea`
+    - **Go**: `go install code.gitea.io/tea/cmd/tea@latest`
+    - **Binary**: Download from [dl.gitea.io](https://dl.gitea.io/tea/)
+2. **`jq`**: JSON processor (required for configuration parsing).
+3. **Authentication**: You must authenticate `tea` with your Gitea instance(s).
+
+## Configuration
+
+The helper uses a JSON configuration file located at `configs/gitea-cli-config.json`.
+
+### Setup
+
+1. Copy the template:
+
+    ```bash
+    cp configs/gitea-cli-config.json.txt configs/gitea-cli-config.json
+    ```
+
+2. Edit `configs/gitea-cli-config.json` with your account details.
+
+### Multi-Account Support
+
+The configuration supports multiple accounts (e.g., `primary`, `work`, `selfhosted`). Each account in the JSON config MUST match a login name configured in `tea`.
+
+**1. Authenticate `tea`:**
+
+```bash
+tea login add --name work --url https://git.company.com --token <your_token>
+tea login add --name personal --url https://gitea.com --token <your_token>
+```
+
+**2. Update `configs/gitea-cli-config.json`:**
+
+```json
+{
+  "accounts": {
+    "work": {
+      "api_url": "https://git.company.com/api/v1",
+      "owner": "your-work-username",
+      "token": "<your_token>", 
+      "default_visibility": "private"
+    },
+    "personal": {
+      "api_url": "https://gitea.com/api/v1",
+      "owner": "your-personal-username",
+      "token": "<your_token>",
+      "default_visibility": "public"
+    }
+  }
+}
+```
+
+*Note: The `token` in the JSON is primarily used for API calls that `tea` doesn't support yet (e.g., creating branches).*
+
+## Usage
+
+Run the helper script:
+
+```bash
+./providers/gitea-cli-helper.sh [command] [account] [arguments]
+```
+
+### Repository Management
+
+- **List Repositories**:
+
+    ```bash
+    ./providers/gitea-cli-helper.sh list-repos personal
+    ```
+
+- **Create Repository**:
+
+    ```bash
+    # Usage: create-repo <account> <name> [desc] [visibility] [auto_init]
+    ./providers/gitea-cli-helper.sh create-repo personal my-new-repo "Description" private true
+    ```
+
+- **Get Repository Details**:
+
+    ```bash
+    ./providers/gitea-cli-helper.sh get-repo personal my-new-repo
+    ```
+
+- **Delete Repository**:
+
+    ```bash
+    ./providers/gitea-cli-helper.sh delete-repo personal my-new-repo
+    ```
+
+### Issue Management
+
+- **List Issues**:
+
+    ```bash
+    ./providers/gitea-cli-helper.sh list-issues personal my-repo open
+    ```
+
+- **Create Issue**:
+
+    ```bash
+    ./providers/gitea-cli-helper.sh create-issue personal my-repo "Bug Title" "Issue description body"
+    ```
+
+- **Close Issue**:
+
+    ```bash
+    ./providers/gitea-cli-helper.sh close-issue personal my-repo 1
+    ```
+
+### Pull Request Management
+
+- **List Pull Requests**:
+
+    ```bash
+    ./providers/gitea-cli-helper.sh list-prs personal my-repo open
+    ```
+
+- **Create Pull Request**:
+
+    ```bash
+    # Usage: create-pr <account> <repo> <title> <head_branch> [base_branch] [body]
+    ./providers/gitea-cli-helper.sh create-pr personal my-repo "Feature X" feature-branch main "Description"
+    ```
+
+- **Merge Pull Request**:
+
+    ```bash
+    # Usage: merge-pr <account> <repo> <pr_number> [method]
+    ./providers/gitea-cli-helper.sh merge-pr personal my-repo 1 squash
+    ```
+
+### Branch Management
+
+- **List Branches**:
+
+    ```bash
+    ./providers/gitea-cli-helper.sh list-branches personal my-repo
+    ```
+
+- **Create Branch**:
+
+    ```bash
+    # Usage: create-branch <account> <repo> <new_branch> [source_branch]
+    ./providers/gitea-cli-helper.sh create-branch personal my-repo feature-branch main
+    ```
+
+## Troubleshooting
+
+- **"Gitea CLI is not authenticated"**: Run `tea login list` to see configured logins. Ensure the `account` name you use in the script command matches one of these logins.
+- **"Owner not configured"**: Check `configs/gitea-cli-config.json` and ensure the `owner` field is set for the account you are using.
+- **API Errors**: Verify your `token` in the configuration file is correct and has sufficient scopes.