git-api-pr
/git-api-pr
GitHub API PR creation without local git. Use when submitting file changes as a PR without local commits — quick fixes, typos, config updates, or bypassing local git state.
- Author
- laurigates ↗
- Repository
- claude-plugins ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
GitHub API PR creation without local git. Use when submitting file changes as a PR without local commits — quick fixes, typos, config updates, or bypassing local git state.
Arguments
/git-api-pr <files...> --title "type(scope): description
Original author description
GitHub API PR creation without local git. Use when submitting file changes as a PR without local commits — quick fixes, typos, config updates, or bypassing local git state.
How it works
- When to Use This Skill
- Context
- Parameters
- Execution
- Error Recovery
- Agentic Optimizations
- See Also
SKILL.md preview
---
name: git-api-pr
description: "GitHub API PR creation without local git. Use when submitting file changes as a PR without local commits — quick fixes, typos, config updates, or bypassing local git state."
args: "<file...> --title <title> [--base <branch>] [--branch <name>] [--body <text>] [--draft] [--delete]"
allowed-tools: Bash(gh api *), Bash(gh pr *), Bash(gh repo *), Bash(base64 *), Bash(git remote *), Bash(mktemp *), Read, TodoWrite
argument-hint: '<files...> --title "type(scope): description"'
disable-model-invocation: true
created: 2026-02-15
modified: 2026-10-09
reviewed: 2026-04-29
---
## When to Use This Skill
| Use this skill when... | Use `/git:commit` instead when... |
|------------------------|-----------------------------------|
| Quick fix to 1-3 files (typos, config, docs) | Complex multi-file refactoring |
| Want a clean workflow without local commits | Need local testing before submitting |
| Submitting changes without touching git state | Need pre-commit hooks to run |
| Want to avoid branch creation/switching locally | Need to stage partial file changes |
| File edits are already done, just need the PR | Need interactive staging (`git add -p`) |
## Context
- Repo: !`git remote -v`
- Default branch (configured): !`git config --default '' --get init.defaultBranch`
- Auth: !`gh auth status`
- Working dir: !`pwd`
## Parameters
Parse these from `$ARGUMENTS`:
| Parameter | Required | Description |
|-----------|----------|-------------|
| `$@` (positional) | Yes | One or more file paths to create/update in the repo |
| `--title <text>` | Yes | PR title — use conventional commit format |
| `--base <branch>` | No | Base branch (default: repo default branch from context) |
| `--branch <name>` | No | New branch name (auto-generated from title if omitted) |
| `--body <text>` | No | PR body/description |
| `--draft` | No | Create as draft PR |
| `--delete` | No | Delete the specified files instead of updating them |
**The scope is required.** Write `type(scope): …` — `docs(readme): update install steps`, never a bare `docs: update install steps`. The Conventional Commits spec lets you omit the scope; this house convention does not (`.claude/rules/conventional-commits.md`). Take it from the component or plugin the change touches. A `--title` with no scope breaks this convention, so add one before creating the PR.
## Execution
Execute this server-side PR creation workflow:
### Step 1: Validate inputs
1. Parse file paths and flags from `$ARGUMENTS`
2. Verify `--title` is provided — error if missing
3. For each file path (unless `--delete`):
- Verify the local file exists using Read tool
- Resolve to a repo-relative path (strip leading `./` or working directory prefix)
4. Determine the repo from context (`$REPO`)
5. Determine base branch: use `--base` if provided, otherwise use default branch from context
### Step 2: Resolve base branch state
```bash
# Get base branch SHA
BASE_SHA=$(gh api repos/$REPO/git/ref/heads/$BASE_BRANCH -q .object.sha)
# Get base tree SHA
BASE_TREE=$(gh api repos/$REPO/git/commits/$BASE_SHA -q .tree.sha)
```
If this fails, the base branch doesn't exist — report error and list available branches.
### Step 3: Generate branch name (if --branch not provided)
Derive from the `--title`:
1. Take the subject part (after `type(scope): `)
2. Convert to kebab-case
3. Prefix with the commit type (e.g., `fix/kebab-subject`)
4. Example: `"fix(api): handle null response"` → `fix/handle-null-response`
### Step 4: Create blobs for each file
For each file path:
```bash
# Base64-encode the file content and create a blob
BLOB_SHA=$(gh api repos/$REPO/git/blobs \
-f content="$(base64 < "$FILE_PATH" | tr -d '\n')" \
-f encoding=base64 \
-q .sha)
```
Track each `{path, blob_sha}` pair for the tree creation in Step 5.
For `--delete` files, skip blob creation — these are handled differently in the tree.
### Step 5: Create tree with all file changes
Build a tree JSON payload and create the tree:
```bash
# Write tree entries to a temp file
TREE_FILE=$(mktemp)
```
For each file to **update/create**, add a tree entry:
```json
{"path": "relative/path/to/file", "mode": "100644", "type": "blob", "sha": "<blob_sha>"}
```
For each file to **delete**, add a tree entry:
```json
{"path": "relative/path/to/file", "mode": "100644", "type": "blob", "sha": null}
```
Create the tree:
```bash
TREE_SHA=$(gh api repos/$REPO/git/trees \
-f base_tree="$BASE_TREE" \
--input "$TREE_FILE" \
-q .sha)
```
Note: The `--input` file must contain the full JSON body with a `tree` array. Example:
```json
{
"base_tree": "<BASE_TREE>",
"tree": [
{"path": "src/config.ts", "mode": "100644", "type": "blob", "sha": "<blob1>"},
{"path": "README.md", "mode": "100644", "type": "blob", "sha": "<blob2>"}
]
}
```
### Step 6: Create commit
```bash
COMMIT_SHA=$(gh api repos/$REPO/git/commits \
-f message="$TITLE" \
-f tree="$TREE_SHA" \
-f "parents[]=$BASE_SHA" \
-q .sha)
```
### Step 7: Create branch ref
```bash
gh api repos/$REPO/git/refs \
-f ref="refs/heads/$BRANCH" \
-f sha="$COMMIT_SHA"
```
If this fails with "Reference already exists", report the error and suggest using a different branch name.
### Step 8: Create PR
When `--body` is provided, write it to a tempfile with the `Write` tool and pass `--body-file`. This sidesteps shell quoting entirely so backticks and code fences in the body render correctly. See the **Body content** rule in `github-issue-writing` for the canonical guidance.
```bash
# Write tool → "$TMP_BODY" (no shell escaping involved)
gh pr create \
--repo "$REPO" \
--head "$BRANCH" \
--base "$BASE_BRANCH" \
--title "$TITLE" \
--body-file "$TMP_BODY"
```
When `--body` is unset, fall back to the trivial-body form `--body "Created via API — no local git operations."`.
Add `--draft` if the flag was provided.
### Step 9: Report results
Print a summary:
```
PR created successfully (no local git changes):
PR: <url>
Branch: <branch> → <base>
Files: <count> file(s) changed
Commit: <sha>
```
### Cleanup
Remove any temp files created during execution.
## Error Recovery
| Error | Recovery |
|-------|----------|
| `gh auth status` fails | "Run `gh auth login` first" |
| Base branch SHA lookup fails | List branches: `gh api repos/$REPO/branches --jq '.[].name'` |
| Blob creation fails | Report which file failed and the API error |
| Branch already exists | Suggest `--branch <different-name>` |
| Tree creation fails | Check if file paths are valid repo-relative paths |
| PR creation fails | Show the API error — common cause is branch protection |
## Agentic Optimizations
| Context | Command |
|---------|---------|
| Single file fix | `/git:api-pr file.ts --title "fix(docs): correct typo"` |
| Multi-file fix | `/git:api-pr a.ts b.ts --title "fix(config): update settings"` |
| Draft PR | `/git:api-pr file.ts --title "feat(api): add endpoint" --draft` |
| Custom branch | `/git:api-pr file.ts --title "fix(api): handle null response" --branch hotfix/issue-123` |
| Delete file | `/git:api-pr old-file.ts --title "chore(scripts): remove deprecated helper" --delete` |
| Non-default base | `/git:api-pr file.ts --title "fix(api): handle null response" --base develop` |
## See Also
- **/git:commit** — full local commit→push→PR workflow (use when you need pre-commit hooks, testing, or complex staging)
- **gh-cli-agentic** — GitHub CLI patterns for JSON output and API access
- **git-branch-pr-workflow** — branch management and PR workflow patterns
Versions
The database has no other skills named git-api-pr.
Database snapshot: 13.11.2026 · package version 65f00d97ea9d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100github-safe-push
Push files to a GitHub repo WITHOUT git branch chaos — uses the GitHub Contents API (PUT) directly, bypassing local git state. Use when local git branches are messy, commits landed on wrong branch, or you need idempotent repo updates. Created after esp-hermes branch-hell. - 90git-checkpoint
Use when the user explicitly asks to commit, create a local Git checkpoint, or prepare focused local commits from an existing working tree. Turn already-completed work into reviewable local Git commits without absorbing unrelated changes, bypassing hooks or pushing. Do not use… - 90managing-git-workflow
Safely inspects repository state and executes explicitly authorized commits, pushes, and pull-request creation through a constrained runner. Use when the user asks to commit selected work, push existing commits, create or inspect a pull request, save changes in Git, or publish a branch to GitHub. - 100git-wtpr
Opens or deletes a git-wt worktree for a GitHub pull request. Use when creating, switching to, or removing a PR worktree. - 100branch-commit-pr
Create a professionally named local git branch, commit the current changes in clean Conventional Commits (no Claude/AI signature), push it, and open a GitHub pull request. Use when the user asks to "make a branch and PR", "commit and open a PR", "ship these changes", or invokes /branch-commit-pr. - 85git-workflow
当用户需要规范化 Git 使用、进行代码协作或管理 Pull Request/Merge Request 时使用。此 Skill 提供 GitHub/Gitee 平台操作、Conventional Commits 规范及 PR/MR 最佳实践指导。