update-mr-desc
Updates merge request descriptions in GitLab by summarizing MR changes into a bulleted list, excluding changes under docs/. Use when updating an MR description via glab MCP or glab CLI, or when the user asks to summarize MR changes for the description.
What this skill does
# Update MR Description Update a merge request's description by inspecting its changes and writing a concise bullet summary. Prefer **glab MCP**; use **glab CLI** when MCP is unavailable. --- ## Workflow 1. **Get the MR diff**. 2. **Filter out docs:** Ignore all changes under the `docs/` path under the project root. 3. **Summarize** the remaining changes into a short bullet list (by intent/feature, not a raw file list). 4. **Show and confirm:** Present the proposed description to the user and wait for explicit confirmation before writing to the remote. 5. **Update the MR description** with that list (only after confirmation). --- ## Getting the diff - **MCP:** Use available tools for the current or specified MR to get the patch. - **CLI:** From the MR branch or repo: `glab mr diff [MR_ID]` (omit MR_ID when one MR is in context). --- ## Excluding docs When building the summary, **do not include** any change whose path: - `docs/` under project root Only summarize changes outside those paths. --- ## Summary format Write 3-8 bullets that describe **what changed and why**, not just file names. **Good:** - Add login endpoint and JWT validation - Extend task model with priority field and migration - Fix date formatting in report export **Bad:** - Changed `src/auth.py` - Changed `src/models/task.py` - Changed `reports.py` Infer intent from diffs (new functions, new fields, renames, fixes) and phrase bullets accordingly. --- ## Updating the description **Always show the proposed description and get user confirmation before writing to the remote.** Do not call the update tool or CLI until the user has approved the text. - **MCP:** Use the MR update tool with the `description` (or equivalent) field set to the new content. Preserve or replace existing description per user preference; if unclear, replace with the new bullet summary. - **CLI:** `glab mr update [MR_ID] --description "$(cat <<'EOF' - Bullet one - Bullet two EOF )"` Escape or quote the description so newlines and bullets are preserved. --- ## Checklist - [ ] Diff retrieved (MCP or CLI) - [ ] All changes under `docs/` excluded from summary - [ ] Summary is bullet and describes intent, not just paths - [ ] Proposed description shown to user and confirmation received - [ ] MR description updated via MCP or `glab mr update` (only after confirmation)
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.