agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/check-my-prs/SKILL.md

check-my-prs

Skill2 starsChanged 19 days agoApache-2.0View on GitHub

Check your open MRs for feedback from reviewers. Shows MRs needing response, awaiting review, pipeline failed, needs rebase, and approved. Use when you want to see PR status, any MR feedback, or before creating more MRs.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Distinctive:

    Check your open MRs for feedback and status.

    line 8
  2. Very specific:

    Use analyze_mr_status (shared parser): status = needs_response | approved | pipeline_failed | needs_rebase | awaiting

    line 38
  3. Distinctive:

    Awaiting Review: no feedback yet

    line 50
  4. Very specific:

    Update state/current_work → open_mrs with pipeline_status, needs_review

    line 54

≈ “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

Check My PRs

Check your open MRs for feedback and status.

Inputs

InputTypeDefaultPurpose
projectstring-GitLab project (resolved from repo_name/cwd)
repo_namestring-Config repo name
show_approvedbooltrueInclude approved MRs
auto_mergeboolfalseAuto-merge approved MRs
auto_rebaseboolfalseAuto-rebase MRs with conflicts
slack_formatboolfalseSlack link format

Workflow

1. Load Persona

  • persona_load("developer")

2. Resolve Project

  • project → repo_name from config → cwd → session project → default automation-analytics/automation-analytics-backend

3. Get Username

  • config.user.username or USER env

4. List My MRs

  • gitlab_mr_list(project, state="opened", author="{my_username}")
  • Parse with parse_mr_list (shared parser)

5. Check First MR

  • gitlab_mr_view(project, mr_id="{first_mr.iid}")
  • Use analyze_mr_status (shared parser): status = needs_response | approved | pipeline_failed | needs_rebase | awaiting

6. Get Feedback Details (if needs_response)

  • gitlab_mr_view again for full comments

7. Auto-rebase (if auto_rebase and needs_rebase)

  • skill_run("rebase_pr", '{"mr_id": {iid}, "force_push": false}')

8. Build Summary

  • Needs Your Response: reviewers, unresolved discussions
  • Needs Rebase: merge conflicts
  • Pipeline Failed: fix CI
  • Awaiting Review: no feedback yet
  • Approved: ready to merge

9. Memory

  • Update state/current_work → open_mrs with pipeline_status, needs_review
  • memory_session_log("Checked {count} PRs", "First MR status: {status}")

10. Learn from Failures

  • VPN: learn_tool_fix("gitlab_mr_list", "no such host", "VPN", "vpn_connect()")
  • Merge conflict: learn_tool_fix("gitlab_mr_merge", "merge conflict", "Conflicts", "skill_run rebase_pr")

MCP Tools

  • persona_load
  • gitlab_mr_list
  • gitlab_mr_view
  • skill_run (rebase_pr)
  • memory_session_log
  • memory_update (state/current_work)
  • learn_tool_fix

Output

  • Categorized MRs with links
  • Quick actions: view comments, merge, rebase
  • PR best practices, known issues

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