一键导入
git-clone
Niels's custom clone commands — `git clone-repo` for permanent work into `~/repos`, and `git clone-repo-tmp` for temporary multi-repo changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Niels's custom clone commands — `git clone-repo` for permanent work into `~/repos`, and `git clone-repo-tmp` for temporary multi-repo changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Niels's custom branch lifecycle commands — create, update, merge, squash, and delete branches with automatic datestamp suffixes. Use these instead of plain `git checkout -b` or `git push`.
Rules for authoring commit messages and PR titles/bodies in Niels's environment — Coop Norge commits guidelines, `git amend` alias, and required Copilot co-author trailer.
Workflow for editing GitHub issue bodies via gh CLI and a local file so changes can be reviewed as a diff before submitting. Use when editing the body of a GitHub issue or RFC.
Discover teams, list members, find team repos, and manage org structure in coopnorge via the GitHub MCP server and gh CLI fallbacks.
Skill for running Mage commands. Mage is a Make-like build tool written in Go, and is used in many of our repos for build and test automation. When a repository contains a `magefile.go` or a `magefiles` directory, you can use this skill to run Mage targets defined in that repository.
Convert a Markdown document to a branded PDF using pandoc + XeLaTeX + eisvogel template, styled with the Coop Masterbrand design tokens (sourced from coopnorge/coop-design-tokens). Use when asked to convert, export, or render a Markdown file to PDF with Coop branding. Triggers on keywords: markdown to pdf, md to pdf, export pdf, pandoc pdf, coop document, branded pdf.
| name | git-clone |
| description | Niels's custom clone commands — `git clone-repo` for permanent work into `~/repos`, and `git clone-repo-tmp` for temporary multi-repo changes. |
| allowed-tools | ["bash"] |
git clone-repo <url> # clones into ~/repos/<host>/<org>/<repo>
Use for single-repo work where the clone should persist.
Use when cloning multiple repos to make broad changes across them.
Do not use for single-repo work — use git clone-repo instead.
Clone from the local repo when possible.
git clone-repo-tmp <url> # clones into /tmp/<random>/<host>/<org>/<repo>, prints the path