DevOps Helper MCP

# GitHub Secrets Management Help the developer manage GitHub Actions secrets for their repository. ## Arguments $ARGUMENTS can be: - empty: Show guide and list secrets - "set NAME": Set a new secret - "list": List all secrets - "delete NAME": Delete a secret ## Steps 1. First check GitHub CLI authentication: ``` gh auth status ``` If not authenticated, guide them through `gh auth login` 2. If no arguments or "list", use `github_secrets_list` tool 3. If setting a secret: - Ask for the secret value (remind them it will be encrypted) - Use `github_secrets_set` tool - Show how to use it in workflows 4. If deleting, use `github_secrets_delete` tool 5. Always show the `github_secrets_guide` for first-time users ## Common Secrets to Set Up For Docker/GHCR workflows: ``` gh secret set DOCKER_USERNAME gh secret set DOCKER_PASSWORD ``` For AWS deployment: ``` gh secret set AWS_ACCESS_KEY_ID gh secret set AWS_SECRET_ACCESS_KEY ``` For database connections: ``` gh secret set DATABASE_URL ``` ## Security Reminders - Never commit secrets to code - GITHUB_TOKEN is automatic - don't set it manually - Use environment secrets (--env production) for sensitive prod credentials - Secrets are masked in logs automatically