القائمة
Detect the git hosting platform (GitHub, GitLab, Bitbucket, …) before running any hosting CLI — creating PRs, viewing issues, commenting on PRs. Never assume GitHub.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | git-platform |
| description | Detect the git hosting platform (GitHub, GitLab, Bitbucket, …) before running any hosting CLI — creating PRs, viewing issues, commenting on PRs. Never assume GitHub. |
Before running any git hosting CLI command (creating PRs, viewing issues, commenting on PRs, etc.), detect the platform first. Never assume GitHub.
Run this detection sequence and use the FIRST match:
git remote get-url origin 2>/dev/null
| Remote URL contains | Platform | CLI | MR/PR term |
|---|---|---|---|
github.com | GitHub | gh | Pull Request (PR) |
gitlab.com or gitlab | GitLab | glab | Merge Request (MR) |
bitbucket.org | Bitbucket | bb or API | Pull Request (PR) |
dev.azure.com or visualstudio.com | Azure DevOps | az repos | Pull Request (PR) |
codecommit | AWS CodeCommit | aws codecommit | Pull Request (PR) |
For self-hosted instances (e.g., gitlab.company.com), check for platform indicators:
.gitlab-ci.yml exists → GitLab.github/ directory exists → GitHubbitbucket-pipelines.yml exists → Bitbucketazure-pipelines.yml exists → Azure DevOps# GitHub
command -v gh &>/dev/null && gh auth status &>/dev/null
# GitLab
command -v glab &>/dev/null && glab auth status &>/dev/null
# Azure DevOps
command -v az &>/dev/null && az devops configure --list &>/dev/null
If the CLI is not installed, inform the user and provide the install command:
brew install gh / sudo apt install ghbrew install glab / sudo apt install glabaz extension add --name azure-devopsUse AskUserQuestion with options:
| Platform | Command |
|---|---|
| GitHub | gh pr create --title "..." --body "..." |
| GitLab | glab mr create --title "..." --description "..." |
| Azure DevOps | az repos pr create --title "..." --description "..." |
| Platform | Command |
|---|---|
| GitHub | gh pr view [N] --json title,body,state,comments |
| GitLab | glab mr view [N] |
| Azure DevOps | az repos pr show --id [N] |
| Platform | Command |
|---|---|
| GitHub | gh pr comment [N] --body "..." |
| GitLab | glab mr note [N] --message "..." |
| Azure DevOps | az repos pr set-vote --id [N] (or API for comments) |
| Platform | Command |
|---|---|
| GitHub | gh pr diff [N] |
| GitLab | glab mr diff [N] |
| Azure DevOps | az repos pr diff --id [N] |
| Platform | Command |
|---|---|
| GitHub | gh issue view [N] --json title,body,comments |
| GitLab | glab issue view [N] |
| Azure DevOps | az boards work-item show --id [N] |
| Platform | Command |
|---|---|
| GitHub | gh pr review [N] --comment --body "..." |
| GitLab | glab mr approve [N] / glab mr note [N] |
| Azure DevOps | az repos pr set-vote --id [N] --vote approve |
| Platform | Command |
|---|---|
| GitHub | gh pr list |
| GitLab | glab mr list |
| Azure DevOps | az repos pr list |
Add a new subcommand to the dotcontext bash CLI (e.g. `dotcontext status`, `dotcontext validate`) — define the command function, route it via the case statement, and wire help and shell completion. Use when extending the CLI surface.
Add a new Claude Code slash command to the dotcontext toolkit — author the command markdown with frontmatter and wire it into the templates and docs. Use when adding a new interactive `/command` workflow that users invoke in Claude Code.
Apply a change safely across many files — refactors touching more than 5 files, library or API migrations, project-wide renames of symbols/imports/paths, or adding boilerplate to many files. Use when "do it all at once" risks context overflow or silent failures.
Reproduce a bug with a failing test before fixing it. Use when investigating a bug, working a bug report or issue, or before attempting any fix — always reproduce first. Pairs with the /fix-bug workflow.
Reproduce a bug with a failing test before fixing it. Use when investigating a bug, working a bug report or issue, or before attempting any fix — always reproduce first. Pairs with the /fix-bug workflow.
Keep external REST API and webhook contracts documented from a single OpenAPI source of truth (docs/openapi.yml), with generated Redoc HTML, validate/build tasks, and a CI step. Use on any change to a public route, request/response shape, auth scheme, or error contract.