← ClaudeAtlas

submit-change-requestlisted

Push a feature branch and open a pull request (GitHub) or merge request (GitLab), wait for CI, fix pipeline failures in scope, and update the linked ClickUp task or repository issue. Use after implementation is verified locally or when the user asks to submit, open a PR/MR, or push for review.
singleton-sd/ai-plattform-skills · ★ 0 · AI & Automation · score 68
Install: claude install-skill singleton-sd/ai-plattform-skills
# Submit Change Request Open a **change request** on the host the target repository uses: - **GitHub** → pull request (PR) - **GitLab** → merge request (MR) Prefer the remote the **target project** treats as authoritative. If the repo mirrors between hosts, submit on the authoritative remote only. ## Resolve host and tracker ### Host Resolve `engineeringHost` in this order (matches [`config/tracker-profiles/`](../../config/tracker-profiles/README.md)): 1. If the user gave a change-request URL → `github.com` → GitHub; `gitlab.com` (or self-hosted GitLab) → GitLab. 2. Else read consumer `.skills/profile` and use `engineeringHost` (`github` | `gitlab`). 3. Else infer from the authoritative remote URL (prefer a remote named `gitlab` / `github` when present; otherwise `origin`): ```bash # Prefer profile when present test -f .skills/profile && jq -r '.engineeringHost // empty' .skills/profile # Fallback: remote URL git remote get-url gitlab 2>/dev/null || git remote get-url origin ``` 4. Confirm CLI auth for that host: `gh auth status` (GitHub) or `glab auth status` (GitLab). Push and open the PR/MR on the **authoritative** remote, not a mirror. In mirrored checkouts, `origin` may be GitHub while `engineeringHost` is `gitlab` (or the reverse) — use the remote that matches the resolved host. ### Tracker The linked work item may be **ClickUp**, a **repository issue**, both, or neither. | Source | Action | |--------|--------| | ClickUp URL / custom ID | Updat