메뉴
Quick local code review of a GitLab MR — checkout, analyze diff, and fix issues directly in the source code. No GitLab API or tokens needed.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | mr-review |
| description | Quick local code review of a GitLab MR — checkout, analyze diff, and fix issues directly in the source code. No GitLab API or tokens needed. |
Lightweight local review of a GitLab MR. Checks out the branch, analyzes the diff, fixes issues directly in source. Uses glab CLI only — no API tokens needed.
For comprehensive workflows (resolving reviewer comments, posting findings to GitLab, git commit/rebase help), use the
gitlab-review-kiranagent instead.
This step is mandatory when a full GitLab URL is given. A bare MR ID (e.g. !42) skips this check.
Parse the project namespace from the URL argument:
Given https://gitlab.com/NAMESPACE/PROJECT/-/merge_requests/ID, extract NAMESPACE/PROJECT.
Get the current repo's remote origin and normalize it:
git remote get-url origin
# SSH: git@gitlab.com:company/camera/camera-build.git → company/camera/camera-build
# HTTPS: https://gitlab.com/company/camera/camera-build.git → company/camera/camera-build
Strip the .git suffix and the host prefix to get the bare NAMESPACE/PROJECT path.
Compare the two project paths:
❌ Repo mismatch detected.
MR URL project : company/camera/camera-soc-yocto
Current repo : company/camera/camera-build
Please cd into the correct repository before running this command.
cd /path/to/camera-soc-yocto
Do not continue past this point if there is a mismatch.
Parse the MR ID or URL from $ARGUMENTS. If not provided, detect the open MR for the current branch.
glab mr view <MR_ID>
glab mr checkout <MR_ID>
glab mr diff <MR_ID>
Read the full diff and surrounding source files for context — don't review the diff in isolation.
Prioritize by impact:
| Priority | Category | Examples |
|---|---|---|
| 🔴 Critical | Security | Injection, exposed secrets, unsafe operations |
| 🔴 Critical | Bugs | Logic errors, null handling, off-by-one, race conditions |
| 🟠 High | Error handling | Missing checks, silent failures, unhandled edge cases |
| 🟡 Medium | Performance | Inefficient loops, unnecessary allocations, blocking calls |
| 🟡 Medium | Code quality | Duplication, excessive complexity, poor naming |
| 🟢 Low | Style | Typos, formatting, minor readability improvements |
For each fix:
## MR Review Summary
**MR**: !<MR_ID> — <title>
**Branch**: <source> → <target>
### Fixed (<count>)
- `<file>:<line>` — <what was fixed and why>
### Noted but not fixed (<count>)
- <description> — <reason skipped (subjective, out of scope, needs discussion)>
### Clean areas
- <areas reviewed that looked good>
Bash commands allowed except:
Creates, formats, and builds documentation compliant with camera-build docs workflow
Fix GitLab MR unresolved comments
Wrap up a GitLab MR — build, deploy & verify on device(s), then generate/update the MR description with full documentation.
Use when diagnosing Ambarella Oryx export muxer H.264/H.265 captures, test_oryx_data_export output, DVR frame corruption, SPS/PPS/IDR fair-clip decoding, or SmartRC/QPM ROI capture validation on camera DUTs.
Search Atlassian Confluence and Jira for content matching a keyword or statement, then produce a structured summary of all relevant findings
Generate a customer-facing SQA release summary for any camera service (rant, bartleby, or others) from a RELEASES.md or changelog file. Looks up Jira tickets, collapses intermediate versions, and outputs a structured markdown file with test commands, QA tips, and a priority test matrix. Use when user says "summarize releases", "release notes for X to Y", "create release summary", "SQA notes", or specifies a version range like "3.2.10 to 3.3.7" for rant, bartleby, or any other camera service.