How do I install the Check My Prs skill?

Run npx skillmds@latest add dmzoneill/check-my-prs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Check My Prs safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Check My Prs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Check My Prs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Check My Prs?

dmzoneill (@dmzoneill) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Check My Prs by dmzoneill — Agent Skill

Name: Check My Prs
Rating: 4.666666666666667 (3 reviews)
Author: dmzoneill

File contents

Check My PRs

Check your open MRs for feedback and status.

Inputs

Input	Type	Default	Purpose
`project`	string	-	GitLab project (resolved from repo_name/cwd)
`repo_name`	string	-	Config repo name
`show_approved`	bool	true	Include approved MRs
`auto_merge`	bool	false	Auto-merge approved MRs
`auto_rebase`	bool	false	Auto-rebase MRs with conflicts
`slack_format`	bool	false	Slack 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

---name: check-my-prsdescription: 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.---# Check My PRsCheck your open MRs for feedback and status.## Inputs| Input | Type | Default | Purpose ||-------|------|---------|---------|| `project` | string | - | GitLab project (resolved from repo_name/cwd) || `repo_name` | string | - | Config repo name || `show_approved` | bool | true | Include approved MRs || `auto_merge` | bool | false | Auto-merge approved MRs || `auto_rebase` | bool | false | Auto-rebase MRs with conflicts || `slack_format` | bool | false | Slack 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

Frequently asked questions

Check My Prs