guided-experience-service-mr-comment-analysis

Analyze unresolved GitLab merge request comments with repository-grounded technical findings.

1|1|Updated Mar 26, 2026

Search Tags:#software engineering #code review #gitlab #merge request #technical analysis #issue triage #repository analysis

One-click install

npx skills add https://github.com/robertolopezlopez/agent-skills --skill guided-experience-service-mr-comment-analysis

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: guided-experience-service-mr-comment-analysis
Source: https://github.com/robertolopezlopez/agent-skills/tree/main/skills/guided-experience-service/mr-comment-analysis
Command: npx skills add https://github.com/robertolopezlopez/agent-skills --skill guided-experience-service-mr-comment-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of analyzing complex merge request feedback by combining review context, repository investigation, and service-specific reasoning into a single actionable workflow.

Core Features & Use Cases

Grouped Comment Analysis: Enriches unresolved merge request issue sections with technical findings, verdicts, risks, and context grounded in the repository.
Repository-Aware Recommendations: Combines GitLab review workflows with repository technical analysis and guided-experience-service-specific contributor practices to propose targeted changes.
Use Case: A maintainer can use this Skill to analyze an unresolved guided-experience-service merge request, validate reviewer concerns against the codebase, and update the main review artifact with proposed fixes.

Quick Start

Use the guided-experience-service-mr-comment-analysis skill to analyze unresolved comments in the specified guided-experience-service merge request and update the main MR artifact with technical analysis and proposed changes.

Frequently Asked Questions about guided-experience-service-mr-comment-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I analyze unresolved GitLab merge request comments to validate code review issues?▼

The workflow combines GitLab review context with repository technical analysis to validate unresolved merge request comments. It enriches grouped review issues with technical findings, verdicts, and risks grounded in the codebase to propose targeted code changes.

What is the best way to turn merge request feedback into actionable code improvements?▼

The best way to turn merge request feedback into actionable code improvements is by combining GitLab review workflows with repository technical analysis and service-specific contributor practices. This approach grounds technical findings in the codebase to propose targeted code changes.

How do I update structured MR analysis artifacts with proposed fixes for unresolved comments?▼

You update structured MR analysis artifacts by integrating GitLab context retrieval and repository analysis processes to investigate unresolved comments. The workflow applies contributor guidance to append technical findings, verdicts, and proposed code changes back into the main artifact.

Does this merge request comment analysis workflow require GitLab context retrieval integration?▼

Yes, this merge request comment analysis workflow requires integration with GitLab context retrieval, repository analysis processes, and contributor guidance. These integrations are necessary to enrich grouped review issues and update the main MR artifact with proposed changes.

Can I use repository technical analysis to investigate GitLab merge request issues?▼

Yes, you can use repository technical analysis to investigate GitLab merge request issues. The workflow enriches unresolved comment sections by grounding technical findings, risks, and verdicts directly in the repository's codebase before proposing targeted code changes.