git-platform

## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Platform Detection](#platform-detection) - [Quick Command Reference](#quick-command-reference) - [Terminology](#terminology) - [Integration Pattern](#integration-pattern) - [Detailed Resources](#detailed-resources) - [Exit Criteria](#exit-criteria) # Git Platform Detection & Command Mapping ## Overview Cross-platform abstraction for git forge operations. Detects whether the current project uses GitHub, GitLab, or Bitbucket, and provides equivalent CLI commands for each platform. The SessionStart hook (`detect-git-platform.sh`) automatically injects the detected platform into session context. This skill provides the command reference for translating operations across platforms. ## When To Use - Before running `gh`, `glab`, or forge API commands - When a skill or command needs to create issues, PRs/MRs, or post comments - When writing CI/CD configuration - Any time forge-specific CLI commands appear in a workflow ## When NOT To Use - Local-only git operations (`git commit`, `git branch`, etc.) - Projects without a hosted git remote ## Platform Detection Detection is automatic via the SessionStart hook. The session context will contain: ``` git_platform: github|gitlab|bitbucket, cli: gh|glab, mr_term: pull request|merge request ``` If you need to re-detect manually: ```bash # Check remote URL git remote get-url origin 2>/dev/null # Check file markers ls -d .github/ .gitlab-ci.yml bitbuc...