agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/close-mr/SKILL.md

close-mr

Skill2 starsChanged 19 days agoApache-2.0View on GitHub

Close a GitLab merge request (abandon). Use when MR is abandoned, replaced, or work no longer needed. Use when user says "close MR", "abandon MR".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If success and mr_info.jira_key and update_jira: jira_add_comment(issue_key, "MR !X was closed.\n\nReason: {reason}")

    line 32
  2. Very specific:

    Remove from state/current_work.open_mrs (filter by mr id)

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Close Merge Request

Inputs

InputTypeDefaultPurpose
mr_idintrequiredGitLab MR ID
projectstringautomation-analytics/automation-analytics-backendGitLab project path
reasonstring"Closing - no longer needed"Reason for closing
update_jirabooltrueAdd comment to linked Jira issue

Workflow

1. Bootstrap

  • persona_load("developer")
  • check_known_issues("gitlab_mr_close")

2. Get MR & Extract Info

  • gitlab_mr_view(project, mr_id) — get details
  • Parse: Jira key (AAP-XXXXX), title, author, source_branch

3. Close MR

  • gitlab_mr_close(project, mr_id)
  • Parse result: success if "closed" or "success" in output

4. Jira & Notify

  • If success and mr_info.jira_key and update_jira: jira_add_comment(issue_key, "MR !X was closed.\n\nReason: {reason}")
  • skill_run("notify_team", '{"message": "MR !X closed for {project}", "channel": "team"}')
  • persona_load("developer") — restore after notify

5. Memory

  • memory_session_log("Closed MR !X", "Title - Reason")
  • Record in learned/patterns.mr_closures
  • Remove from state/current_work.open_mrs (filter by mr id)

6. Cleanup Branch

  • Resolve repo path from config (match project to gitlab)
  • skill_run("cleanup_branches", '{"repo": "...", "dry_run": false}') — delete source branch
  • persona_load("developer") — restore

7. Failure Learning

  • "no such host" → learn_tool_fix("gitlab_mr_close", "no such host", "VPN", "vpn_connect()")
  • "merge request not found" → learn_tool_fix("gitlab_mr_close", "merge request not found", "Wrong ID/project", "Check mr_id and project")
  • "already closed" → no action needed

Key MCP Tools

  • persona_load, gitlab_mr_view, gitlab_mr_close
  • jira_add_comment
  • check_known_issues, learn_tool_fix
  • memory_session_log, skill_run

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free