agentleFS
Sign inStart free
aniketshukla1aniketshukla1/sdlc-kit/.cursor/skills/gitlab-mr/SKILL.md

gitlab-mr

Skill1 starsChanged 12 days agoMITView on GitHub

Phase 7. Commits, rebases, pushes the branch and opens the merge request (a pull request on GitHub), then links it on the ticket. Use after self-review is done and run-checks prints ALL PASS.

  • Reads credentials
  • Commits and pushes

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 1 is distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

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

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

    Run /run-checks now. Continue only on ALL PASS.

    line 8
  2. Very specific:

    Check what will be committed: git status --short.

    line 9
  3. Very specific:

    Must NOT appear: .agent/work/, .env files, build output, files not in PLAN.md.

    line 10
  4. Very specific:

    Commit, one commit per logical part (e.g.

    line 12
  5. Very specific:

    Update with main: git fetch origin && git rebase origin/main.

    line 15
  6. Distinctive:

    After a rebase, run /run-checks again (2 Alembic heads → /db-migration step 7).

    line 17
  7. Very specific:

    Create the MR (GitLab or GitHub.

    line 24
  8. Very specific:

    Add --draft at the end if "Human actions required" is not None.

    line 26
  9. Very specific:

    Verify: it prints a URL ending in /merge_requests/<IID> or /pull/<IID>.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Open the MR (phase 7)

Steps

  1. Run /run-checks now. Continue only on ALL PASS.
  2. Check what will be committed: git status --short. Must NOT appear: .agent/work/, .env files, build output, files not in PLAN.md.
  3. Stage files explicitly: git add <file> <file> ... (never git add -A or git add .).
  4. Commit, one commit per logical part (e.g. migration, backend, frontend, tests): git commit -m "<KEY>: <type>(<scope>): <imperative summary, ≤ 72 chars>" <type> = feat | fix | refactor | test | chore. Example: PROJ-123: feat(orders): add cancel endpoint
  5. Update with main: git fetch origin && git rebase origin/main. Conflict in a file you did not change, or you're unsure → git rebase --abort and ask the human. After a rebase, run /run-checks again (2 Alembic heads → /db-migration step 7).
  6. Push: git push -u origin HEAD. Never --force. If a push is rejected, ask the human.
  7. Proof: bash .cursor/skills/run-checks/scripts/proof_pack.sh > .agent/work/<KEY>/proof.md. It refuses if anything changed after the last ALL PASS (an edit, a commit, a rebase): run /run-checks, commit any fix, push, and run it again. Never write or edit the proof by hand.
  8. Fill mr-template.md (next to this file) into .agent/work/<KEY>/MR.md. Every section, or None. The Proof section is proof.md, pasted unedited.
  9. Create the MR (GitLab or GitHub; mr.sh picks the host): bash .cursor/skills/mr-feedback/scripts/mr.sh create "<KEY>: <summary>" .agent/work/<KEY>/MR.md Add --draft at the end if "Human actions required" is not None. Verify: it prints a URL ending in /merge_requests/<IID> or /pull/<IID>. The IID is that number.
  10. Save MR URL and IID in PROGRESS.md. Set Phase: 7-mr (open). PROGRESS.md has Parent: <KEY>? Also set this sub-task's row in that parent's Roadmap (its PLAN.md) to MR !<IID>.
  11. Post a comment (tracker MCP) on the ticket, and on its parent if it has one: Agent: MR ready for review: <url>. A CHAT-<n> key has no ticket: skip this.
  12. Tell the human: MR created: <url>. After review or a pipeline result, start a new chat and type: Continue <KEY>.

Done when

  • Only planned files committed, commit messages follow the format
  • Branch pushed without force, MR created against main
  • The MR's Proof section is proof_pack.sh output for the pushed head, unedited
  • MR URL in PROGRESS.md and on the ticket

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