platform.gitlab.gitlab-commit-review-workflow
Use for narrow GitLab commit review runs triggered from commit comments.
Best use case
platform.gitlab.gitlab-commit-review-workflow is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use for narrow GitLab commit review runs triggered from commit comments.
Teams using platform.gitlab.gitlab-commit-review-workflow should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gitlab-commit-review-workflow/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How platform.gitlab.gitlab-commit-review-workflow Compares
| Feature / Agent | platform.gitlab.gitlab-commit-review-workflow | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use for narrow GitLab commit review runs triggered from commit comments.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# GitLab Commit Review Workflow Review the target commit in a narrow scope. Prefer direct changed-line feedback and avoid broad architectural conclusions unless the commit clearly touches shared production behavior. Commit review may skip spec-gate work when the request is only asking for localized feedback. Security and QA review still apply when the diff touches auth, permissions, storage, networking, dependency execution, runtime configuration, release scripts, or user data.
Related Skills
platform.gitlab.verification-matrix
Use to plan minimal QA checks for GitLab review findings.
platform.gitlab.subagent-prompts.tech-architect
Prompt template for the GitLab review technical architecture custom subagent.
platform.gitlab.subagent-prompts.spec-writer
Prompt template for the GitLab review discovery and spec context custom subagent.
platform.gitlab.subagent-prompts.security-agent
Prompt template for the GitLab review security custom subagent.
platform.gitlab.subagent-prompts.risk-qa
Prompt template for the GitLab review QA and risk custom subagent.
platform.gitlab.subagent-prompts.frontend-designer
Prompt template for the GitLab review frontend design custom subagent.
platform.gitlab.subagent-prompts.developer
Prompt template for the GitLab review developer custom subagent.
platform.gitlab.subagent-prompts.auto-fixer
Prompt template for the GitLab review auto fixer custom subagent.
platform.gitlab.spec-gate-review
Use to decide whether a GitLab review has enough product and technical context to proceed.
platform.gitlab.security-review-policy
Use for security review of GitLab MR or commit diffs.
platform.gitlab.review-finding-schema
Use to produce structured GitLab code review findings and the final GitLab review result.
platform.gitlab.pm-risk-routing
Use to choose which custom subagents should be created for a GitLab review run.