with one click
mr-fix
Fix GitLab MR unresolved comments
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Fix GitLab MR unresolved comments
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Creates, formats, and builds documentation compliant with camera-build docs workflow
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.
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.
| name | mr-fix |
| description | Fix GitLab MR unresolved comments |
Step 1: Run this command to get unresolved comments for a MR (script must be in $PATH):
glab-unresolved.sh <MR_URL>
Step 2: For each unresolved comment, evaluate and act:
Step 3: Commit your fixes as a NEW commit (never amend HEAD). Group related fixes into a single commit when they address the same concern. Use this commit message format:
fix: address MR review feedback
- <brief description of each fix>
Step 4: After all comments are processed, print a summary:
## MR Review Fix Summary
- Fixed: <count> comments
- <file:line> — <what was fixed>
- Skipped: <count> comments
- <reason> — <comment excerpt>
Step 5: ASK to push changes or post comments to GitLab. This will be done manually.
Bash commands allowed except: