一键在 Manus 中运行任何 Skill

git-fix-pr

星标0

分支0

更新时间2026年6月10日 19:42

Analyze and fix failing PR checks. Use when the user asks to fix the PR, resolve failing CI checks, diagnose red GitHub Actions runs, auto-fix lint/type/test failures on a pull request, or reproduce CI errors locally before pushing corrections.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

meaganewaller

meaganewaller/marketplace

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Context

Repo: !git remote get-url origin
Current branch: !git branch --show-current
Git status: !git status --porcelain=v2 --branch
Staged changes: !git diff --cached --numstat
Unstaged changes: !git diff --numstat
Recent commits: !git log --format='%h %s' --max-count=5

Parameters

Parse these parameters from the command (all optional):

$1: PR number (if not provided, detect from current branch)
--auto-fix: Automatically apply fixes for common issues
--push: Push fixes to the branch after committing

Your task

Analyze and fix failing PR checks.

Step 1: Determine PR

Get PR number from argument or detect from current branch
Fetch PR status using gh pr checks <pr-number> or mcp__github__pull_request_read

Step 2: Analyze Failures

Identify failing checks from PR status
Research error messages in workflow logs
Categorize failures:
- Linting errors
- Type errors
- Test failures
- Build errors

Step 3: Reproduce Locally

Run tests locally to reproduce issues
Run linters to check for style issues
Run type checker if applicable

Step 4: Apply Fixes (if --auto-fix)

Based on failure type:

Linting errors: Run appropriate linters/formatters

# Python
uv run ruff check --fix .
uv run ruff format .

# JavaScript/TypeScript
npm run lint -- --fix

Type errors: Fix type annotations or implementations
Test failures: Fix failing tests or implementation bugs

Step 5: Commit and Push (if --push)

Stage fixes: git add -u
Commit: git commit -m "fix: resolve CI failures"
Push: git push

Step 6: Verify

Re-run checks locally to verify fixes
Monitor PR checks after push

Common Fix Patterns

Check Type	Common Fixes
Linting	Run formatter, fix import order
Types	Add type annotations, fix mismatches
Tests	Fix assertions, update snapshots
Build	Fix imports, resolve dependencies

Guides fnox secrets management configuration via fnox.toml — file structure, secrets definition, profiles, hierarchical config, mise integration, import/export, and sync. Always use fnox as a mise integration, never as standalone shell integration. Triggers on: "set up fnox", "fnox.toml", "configure fnox", "fnox profiles", "fnox secrets", "mise fnox", "migrate to fnox", "fnox sync", "fnox import", "fnox export".

2026-06-100

fnox-providers

meaganewaller/marketplace

Guides fnox provider selection and setup — age encryption, AWS (Parameter Store and Secrets Manager), 1Password, Bitwarden, GCP, Azure, Doppler, Vault, and local options. Triggers on: "set up fnox provider", "fnox age", "fnox aws", "fnox 1password", "which fnox provider", "configure fnox provider", "fnox encryption", "add provider to fnox".

2026-06-100

fnox-security

meaganewaller/marketplace

Security best practices for fnox — key rotation, gitignore rules, CI/CD secret handling, access control, missing-secret enforcement, and avoiding common mistakes. Triggers on: "fnox security", "rotate fnox keys", "fnox gitignore", "fnox ci secrets", "fnox key rotation", "fnox access control", "fnox reencrypt", "secure fnox setup", "fnox best practices".

2026-06-100

git-api-pr

meaganewaller/marketplace

Create PRs via GitHub API without local git operations. Use when you want to submit file changes as a PR without committing locally — for quick fixes, typos, config updates, or when you want a clean workflow that bypasses local git state entirely.

2026-06-100

git-commit-push-pr

meaganewaller/marketplace

Complete workflow from changes to PR - auto-detect related issues, create logical commits with proper issue linkage, push to remote feature branch, and create pull request. Use when user says "create pr", "let's pr", "commit and pr", "push and create pr", or wants to go from uncommitted changes to an open pull request in one step.

2026-06-100

created	"2026-04-23T00:00:00.000Z"
modified	"2026-04-23T00:00:00.000Z"
reviewed	"2026-04-23T00:00:00.000Z"
allowed-tools	Bash(gh pr checks ), Bash(gh pr view ), Bash(gh run view ), Bash(gh run list ), Bash(gh repo view ), Bash(git status ), Bash(git diff ), Bash(git log ), Bash(git add ), Bash(git commit ), Bash(git push ), Bash(pre-commit ), Bash(npm run ), Bash(uv run ), Read, Edit, Grep, Glob, TodoWrite, mcp__github__pull_request_read
args	[pr-number] [--auto-fix] [--push]
argument-hint	[pr-number] [--auto-fix] [--push]
disable-model-invocation	true
description	Analyze and fix failing PR checks. Use when the user asks to fix the PR, resolve failing CI checks, diagnose red GitHub Actions runs, auto-fix lint/type/test failures on a pull request, or reproduce CI errors locally before pushing corrections.
name	git-fix-pr

Context

Repo: !git remote get-url origin
Current branch: !git branch --show-current
Git status: !git status --porcelain=v2 --branch
Staged changes: !git diff --cached --numstat
Unstaged changes: !git diff --numstat
Recent commits: !git log --format='%h %s' --max-count=5

Parameters

Parse these parameters from the command (all optional):

$1: PR number (if not provided, detect from current branch)
--auto-fix: Automatically apply fixes for common issues
--push: Push fixes to the branch after committing

Your task

Analyze and fix failing PR checks.

Step 1: Determine PR

Get PR number from argument or detect from current branch
Fetch PR status using gh pr checks <pr-number> or mcp__github__pull_request_read

Step 2: Analyze Failures

Identify failing checks from PR status
Research error messages in workflow logs
Categorize failures:
- Linting errors
- Type errors
- Test failures
- Build errors

Step 3: Reproduce Locally

Run tests locally to reproduce issues
Run linters to check for style issues
Run type checker if applicable

Step 4: Apply Fixes (if --auto-fix)

Based on failure type:

Linting errors: Run appropriate linters/formatters

# Python
uv run ruff check --fix .
uv run ruff format .

# JavaScript/TypeScript
npm run lint -- --fix

Type errors: Fix type annotations or implementations
Test failures: Fix failing tests or implementation bugs

Step 5: Commit and Push (if --push)

Stage fixes: git add -u
Commit: git commit -m "fix: resolve CI failures"
Push: git push

Step 6: Verify

Re-run checks locally to verify fixes
Monitor PR checks after push

Common Fix Patterns

Check Type	Common Fixes
Linting	Run formatter, fix import order
Types	Add type annotations, fix mismatches
Tests	Fix assertions, update snapshots
Build	Fix imports, resolve dependencies

git-fix-pr

Context

Parameters

Your task

Step 1: Determine PR

Step 2: Analyze Failures

Step 3: Reproduce Locally

Step 4: Apply Fixes (if --auto-fix)

Step 5: Commit and Push (if --push)

Step 6: Verify

Common Fix Patterns

See Also

Context

Parameters

Your task

Step 1: Determine PR

Step 2: Analyze Failures

Step 3: Reproduce Locally

Step 4: Apply Fixes (if --auto-fix)

Step 5: Commit and Push (if --push)

Step 6: Verify

Common Fix Patterns

See Also

git-fix-pr

Context

Parameters

Your task

Step 1: Determine PR

Step 2: Analyze Failures

Step 3: Reproduce Locally

Step 4: Apply Fixes (if --auto-fix)

Step 5: Commit and Push (if --push)

Step 6: Verify

Common Fix Patterns

See Also

同仓库更多 Skills

同仓库更多 Skills

Context

Parameters

Your task

Step 1: Determine PR

Step 2: Analyze Failures

Step 3: Reproduce Locally

Step 4: Apply Fixes (if --auto-fix)

Step 5: Commit and Push (if --push)

Step 6: Verify

Common Fix Patterns

See Also