BytesAgain is a curated directory of 60,000+ AI agent skills from ClawHub, GitHub, LobeHub, and Dify. Search skills by keyword in 7 languages, browse by role (developer, creator, trader, marketer) or by use case.

How do I find AI skills on BytesAgain?

Use the search bar on BytesAgain.com to search by keyword in 7 languages. You can also browse by role (developer, creator, trader, marketer) or by use case. Each skill shows install instructions for Claude, Cursor, OpenClaw, Continue, and more.

Yes, BytesAgain is completely free. No registration required for searching skills. The MCP API is also free with rate limits.

Does BytesAgain have an API for AI agents?

Yes! BytesAgain provides a free MCP SSE endpoint at /api/mcp/sse for AI agents, plus a REST API at /api/mcp?action=search&q= . No authentication needed.

Can I request a new AI skill on BytesAgain?

Yes! Visit the Requests page on BytesAgain.com to submit a skill request. Your request will be visible to the community and notified to the site admin.

GitLab MR Code Review — AI Agent Skill | BytesAgain

📖 About This Skill

name: gitlab-auto-review description: > Automated AI code review for GitLab Merge Requests via polling. Periodically checks for open MRs, reviews code diffs for security vulnerabilities, bugs, and best practices, then posts inline comments and a summary note on GitLab. Supports project-level custom review rules via .gitlab-review-prompt.md. Use when: setting up MR code review, configuring GitLab review automation, checking MR review status, or troubleshooting GitLab MR review issues. metadata: openclaw: requires: bins: ["node"] env: ["GITLAB_URL", "GITLAB_TOKEN"] primaryEnv: "GITLAB_TOKEN"

GitLab MR Code Review

Polling-based automated code review for GitLab MRs.

Architecture

Cron (*/2 * * * *) → gitlab-api.js list-mrs → skip reviewed → fetch diff → AI review → post comments/note

No webhook server — pure polling

Reviewed MRs tracked in {baseDir}/mr-reviewed.json

Setup

1. Create {baseDir}/.env with your GitLab credentials:

   GITLAB_URL=https://gitlab.example.com
   GITLAB_TOKEN=glpat-xxxxxxxxxxxxxxxxxxxx

The script auto-loads this file. Environment variables take precedence (won't be overwritten if already set). 2. Test: node {baseDir}/scripts/gitlab-api.js get-version 3. Install cron worker — see references/cron-setup.md for the full command

API Script Reference

node {baseDir}/scripts/gitlab-api.js get-version                              # Test connection
node {baseDir}/scripts/gitlab-api.js list-mrs                                 # List open MRs
node {baseDir}/scripts/gitlab-api.js list-mrs --project         # Filter by project
node {baseDir}/scripts/gitlab-api.js get-changes          # Fetch MR diff
node {baseDir}/scripts/gitlab-api.js get-file       # Fetch file content
node {baseDir}/scripts/gitlab-api.js post-comment --file      # Inline comment (use --file!)
node {baseDir}/scripts/gitlab-api.js post-note   '' # Summary note

post-comment JSON format

{
  "body": "[Critical] sql_injection\n\nRaw query with user input.",
  "position": {
    "base_sha": "abc123",
    "start_sha": "def456",
    "head_sha": "ghi789",
    "new_path": "src/db.js",
    "new_line": 42
  }
}

base_sha/start_sha/head_sha come from get-changes output's diff_refs.

Review Rules

Default: references/review-guidelines.md — severity levels, output format, what to skip

Per-project: Place .gitlab-review-prompt.md in the repo root; the worker auto-fetches it via get-file

Troubleshooting

| Problem | Fix | |---------|-----| | MRs not reviewed | openclaw cron list — is worker enabled? | | API errors | node {baseDir}/scripts/gitlab-api.js get-version | | Duplicate reviews | Check {baseDir}/mr-reviewed.json exists and is writable; ensure cron prompt has explicit "never re-review" rule at highest priority | | Garbled comments | Use --file mode for post-comment (Windows PowerShell encoding) | | Wrong line numbers | new_line must be the line number in the NEW version of the file |

⚙️ Configuration

1. Create {baseDir}/.env with your GitLab credentials:

   GITLAB_URL=https://gitlab.example.com
   GITLAB_TOKEN=glpat-xxxxxxxxxxxxxxxxxxxx

The script auto-loads this file. Environment variables take precedence (won't be overwritten if already set). 2. Test: node {baseDir}/scripts/gitlab-api.js get-version 3. Install cron worker — see references/cron-setup.md for the full command

📋 Tips & Best Practices

| Problem | Fix | |---------|-----| | MRs not reviewed | openclaw cron list — is worker enabled? | | API errors | node {baseDir}/scripts/gitlab-api.js get-version | | Duplicate reviews | Check {baseDir}/mr-reviewed.json exists and is writable; ensure cron prompt has explicit "never re-review" rule at highest priority | | Garbled comments | Use --file mode for post-comment (Windows PowerShell encoding) | | Wrong line numbers | new_line must be the line number in the NEW version of the file |