Verified:GitHub

fdl-glab-review-plan

Generate an ordered implementation plan from GitLab merge request reviewer discussions.

Updated Aug 23, 2026

Search Tags:#automation #code review #task planning #gitlab #merge request #validation gates #execution contract

One-click install

npx skills add https://github.com/janezlapajne/dotfiles --skill fdl-glab-review-plan

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: fdl-glab-review-plan
Source: https://github.com/janezlapajne/dotfiles/tree/main/conf/dotfiles/claude/skills/fdl-glab-review-plan
Command: npx skills add https://github.com/janezlapajne/dotfiles --skill fdl-glab-review-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts open reviewer discussion threads from a GitLab merge request into a structured, ordered implementation plan so the feedback can be executed end-to-end without losing context.

Core Features & Use Cases

Automated task grouping: Groups your numbered in-thread replies (e.g., 1, 2, (3)) into atomic tasks, while unnumbered threads become separate ungrouped items.
Executor-ready contract: Outputs fixed four-step blocks (Implement → Cleanup → Validate → Post resolution) with the exact discussion and note IDs needed for downstream actions.
Read-only planning with guardrails: Reads MR metadata and discussions, filters to open unresolved items, and includes per-thread validation gates to prevent misleading resolutions.

Quick Start

Paste a GitLab merge request URL and ask for “the plan to address reviews”, then follow the emitted tasks with your executor skill.

Frequently Asked Questions about fdl-glab-review-plan

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

FAQPage Schema

How do I turn GitLab merge request review comments into an actionable task plan?▼

To turn GitLab merge request review comments into a task plan, use a tool that parses open unresolved discussion threads and groups numbered replies into atomic executable tasks with validation gates. This converts reviewer feedback into an ordered implementation plan.

Can I group numbered in-thread replies from GitLab merge requests into separate tasks?▼

Yes, you can group numbered in-thread replies from GitLab merge requests into separate tasks. The skill parses numbered markers like 1, 2, and (3) to group threads into atomic tasks, while unnumbered threads become separate ungrouped items.

What is the best way to track unresolved GitLab merge request discussions for implementation?▼

The best way to track unresolved GitLab merge request discussions is to extract open threads and map them to a structured execution contract. This generates an ordered plan containing raw discussion and note IDs required for downstream automation.

Does this code review planning tool modify the GitLab merge request state during task generation?▼

No, this code review planning tool does not modify the GitLab merge request state. It operates as a read-only planning step that inspects MR metadata and discussions via glab or GitLab MCP tools to ensure the merge request remains untouched.

How do I resolve GitLab merge request reviewer threads automatically after implementing changes?▼

To resolve GitLab merge request reviewer threads after implementing changes, follow a four-step execution contract that includes Implement, Cleanup, Validate, and Post resolution phases. The plan outputs the exact discussion and note IDs needed for these downstream actions.

What do I need to generate an implementation plan from GitLab merge request feedback?▼

To generate an implementation plan from GitLab merge request feedback, you need the merge request URL and access to glab or GitLab MCP tools. The skill reads the MR state to filter open unresolved items and outputs a validation-gated execution contract.