원클릭으로 Manus에서 모든 스킬 실행

$pwd:

custom-dependency-pr-solver

Name: Custom Dependency Pr Solver
Author: equinor

// Batch-process Dependabot PRs end-to-end: checkout, rebase, review, changeset, validate, and auto-merge high-confidence PRs. USE FOR: process all Dependabot PRs, clear dependency backlog, batch-merge safe Dependabot updates, batch-process dependency PRs. DO NOT USE FOR: single-PR deep review (use fusion-dependency-review), feature PRs, non-Dependabot dependency PRs, or PRs requiring manual code changes.

Manus에서 실행

$ git log --oneline --stat

stars:9

forks:8

updated:2026년 4월 21일 10:10

파일 탐색기

4 개 파일

SKILL.md

readonly

name	custom-dependency-pr-solver
description	Batch-process Dependabot PRs end-to-end: checkout, rebase, review, changeset, validate, and auto-merge high-confidence PRs. USE FOR: process all Dependabot PRs, clear dependency backlog, batch-merge safe Dependabot updates, batch-process dependency PRs. DO NOT USE FOR: single-PR deep review (use fusion-dependency-review), feature PRs, non-Dependabot dependency PRs, or PRs requiring manual code changes.
license	MIT
compatibility	Requires GitHub CLI (`gh`) authenticated with admin merge rights. Requires pnpm and the Fusion Framework monorepo build toolchain.
metadata	{"version":"0.1.0","status":"experimental","owner":"@equinor/fusion-core","tags":["github","dependabot","dependency-updates","batch-workflow","auto-merge"],"mcp":{"suggested":["github"]}}

Dependency PR Solver

Batch workflow that processes open Dependabot PRs sequentially. Delegates per-PR research, lens analysis, and verdicts to fusion-dependency-review. This skill owns batch orchestration, source-control operations, changeset creation, auto-merge, and reporting.

When to use

Typical triggers:

"Process all open Dependabot PRs"
"Clear the dependency PR backlog"
"Batch-process dependency PRs"
"Batch-merge safe Dependabot updates"
"Solve all dependency PRs"

When not to use

Deep single-PR review → use fusion-dependency-review
Feature PRs or application code reviews
PRs requiring manual code changes beyond changesets
When you lack admin merge rights

Required inputs

Repository: owner and name (infer from workspace when possible)
Confirmation: explicit user approval before starting the batch

Optional: PR filter (include/exclude numbers), --review-only (skip merge), --merge-medium (merge medium-confidence too).

Delegation

This skill delegates per-PR analysis to fusion-dependency-review:

Research — upstream changelog, breaking changes, security, existing discussion
Lens analysis — security, code quality, impact assessments
Verdict — recommendation and confidence scoring

Changeset rules, confidence criteria, rebase strategy, and validation commands follow .github/instructions/dependabot-pr.instructions.md.

Instructions

Step 1 — List and triage

gh pr list --author "app/dependabot" --state open --json number,title,headRefName,baseRefName,mergeable,statusCheckRollup

Present a summary table and ask the user to confirm which PRs to process or confirm "all".

Step 2 — Process each PR sequentially

For each confirmed PR, execute Steps 3–7. If a PR fails at any step, log the failure, skip to the next, and include it in the final report.

Step 3 — Checkout and rebase

Follow the rebase strategy in .github/instructions/dependabot-pr.instructions.md:

git fetch origin <base-branch> && gh pr checkout <number>
git rebase origin/<base-branch>
On conflict: abort, mark needs-manual-intervention, skip.
git push --force-with-lease
pnpm install --frozen-lockfile (if lockfile drifts: pnpm install, commit, push).

Step 4 — Review via fusion-dependency-review

Run the fusion-dependency-review workflow for this PR:

Research upstream changes and existing PR discussion.
Assess security, code quality, and impact.
Post a research comment using assets/research-comment-template.md.
Produce a confidence score (high / medium / low) using the criteria in .github/instructions/dependabot-pr.instructions.md.

Keep research focused — do not deep-dive unless a concern surfaces.

Step 5 — Create changesets

Follow the changeset decision rules in .github/instructions/dependabot-pr.instructions.md. Create, commit, and push changesets for affected published packages.

Step 6 — Validate

pnpm test && pnpm build && pnpm -w check

On failure: attempt trivial fixes (e.g., pnpm format). If non-trivial, mark needs-manual-intervention.

Step 7 — Merge or report

High confidence:

Post verdict comment using assets/verdict-comment-template.md.
gh pr merge <number> --squash --admin

Medium or low confidence:

Post verdict comment with findings.
Do not merge. Include in final report.

Step 8 — Final batch report

PR	Title	Status	Confidence	Action
#N	...	merged / skipped / failed	high/med/low	merged / needs review / needs intervention

Expected output

Research and verdict comments posted to each processed PR
Changesets created where required
High-confidence PRs merged via admin squash
Final batch summary table
List of PRs needing manual intervention with reasons

Safety & constraints

This skill is mutation-capable. .github/instructions/dependabot-pr.instructions.md takes precedence on conflicts.

Never:

Merge without posting research and verdict comments first
Merge a PR with failing validation
Merge major version bumps without explicit user override
Merge the base branch into a Dependabot PR branch (rebase only)
Force-push without --force-with-lease
Process PRs without initial user confirmation

Always:

Return to main after batch processing is complete

related-skills.json

같은 저장소

fusion-mcp.md

from "equinor/fusion-framework"

Explain what Fusion MCP is and guide users through setting it up when they need Fusion-aware MCP capabilities in Copilot workflows.

2026-04-309

fusion-dependency-review.md

from "equinor/fusion-framework"

Review dependency PRs with structured research, existing-PR-discussion capture, multi-lens analysis (security, code quality, impact), and a repeatable verdict template. USE FOR: dependency update PRs, Renovate/Dependabot PRs, library upgrade reviews, "review this dependency PR", "should we merge this update". DO NOT USE FOR: feature PRs, application code reviews, dependency automation/bot configuration, or unattended merge without confirmation.

2026-04-209

fusion-issue-authoring.md

from "equinor/fusion-framework"

Classify issue type, activate the matching agent mode for type-specific drafting, and enforce shared safety gates before GitHub mutation.

2026-04-209

fusion-issue-solving.md

from "equinor/fusion-framework"

Handles GitHub issue resolution end-to-end for prompts like "solve #123", "lets solve #123", "work on #123", "work on https://github.com/owner/repo/issues/123", or by pasting a direct GitHub issue URL as the request. USE FOR: solve #123, continue work on issue #123, work on https://github.com/owner/repo/issues/123, paste a GitHub issue URL for implementation work. DO NOT USE FOR: issue drafting only, PR review only, or non-implementation research.

2026-04-209

fusion-issue-task-planning.md

from "equinor/fusion-framework"

Plan and break down user-story issues into ordered, traceable task issue drafts with explicit publish gates.

2026-04-209

custom-index-eval.md

from "equinor/fusion-framework"

Iterative evaluation of Fusion Framework MCP search quality against documented domain patterns. Loads domain files from eval/index/, queries Fusion MCP for each pattern, validates recall against must/should requirements, and produces a human-readable pass/fail report. USE FOR: eval core, eval all, evaluate MCP index accuracy, validate search recall for a domain, check index freshness. DO NOT USE FOR: writing domain patterns, populating eval/index/ files, running CI pipelines, or batch automation.

2026-03-189

package.json

"author": "equinor"

"repository": "equinor/fusion-framework"

GitHub 저장소 열기 Creator 저장소 보기

$ install --global

$ download --local

Manus에서 실행

$ useful --forSOC

소프트웨어 개발자컴퓨터 및 수학직15-1252L4

name	custom-dependency-pr-solver
description	Batch-process Dependabot PRs end-to-end: checkout, rebase, review, changeset, validate, and auto-merge high-confidence PRs. USE FOR: process all Dependabot PRs, clear dependency backlog, batch-merge safe Dependabot updates, batch-process dependency PRs. DO NOT USE FOR: single-PR deep review (use fusion-dependency-review), feature PRs, non-Dependabot dependency PRs, or PRs requiring manual code changes.
license	MIT
compatibility	Requires GitHub CLI (`gh`) authenticated with admin merge rights. Requires pnpm and the Fusion Framework monorepo build toolchain.
metadata	{"version":"0.1.0","status":"experimental","owner":"@equinor/fusion-core","tags":["github","dependabot","dependency-updates","batch-workflow","auto-merge"],"mcp":{"suggested":["github"]}}

Dependency PR Solver

When to use

Typical triggers:

"Process all open Dependabot PRs"
"Clear the dependency PR backlog"
"Batch-process dependency PRs"
"Batch-merge safe Dependabot updates"
"Solve all dependency PRs"

When not to use

Deep single-PR review → use fusion-dependency-review
Feature PRs or application code reviews
PRs requiring manual code changes beyond changesets
When you lack admin merge rights

Required inputs

Repository: owner and name (infer from workspace when possible)
Confirmation: explicit user approval before starting the batch

Optional: PR filter (include/exclude numbers), --review-only (skip merge), --merge-medium (merge medium-confidence too).

Delegation

This skill delegates per-PR analysis to fusion-dependency-review:

Research — upstream changelog, breaking changes, security, existing discussion
Lens analysis — security, code quality, impact assessments
Verdict — recommendation and confidence scoring

Changeset rules, confidence criteria, rebase strategy, and validation commands follow .github/instructions/dependabot-pr.instructions.md.

Instructions

Step 1 — List and triage

gh pr list --author "app/dependabot" --state open --json number,title,headRefName,baseRefName,mergeable,statusCheckRollup

Present a summary table and ask the user to confirm which PRs to process or confirm "all".

Step 2 — Process each PR sequentially

For each confirmed PR, execute Steps 3–7. If a PR fails at any step, log the failure, skip to the next, and include it in the final report.

Step 3 — Checkout and rebase

Follow the rebase strategy in .github/instructions/dependabot-pr.instructions.md:

git fetch origin <base-branch> && gh pr checkout <number>
git rebase origin/<base-branch>
On conflict: abort, mark needs-manual-intervention, skip.
git push --force-with-lease
pnpm install --frozen-lockfile (if lockfile drifts: pnpm install, commit, push).

Step 4 — Review via fusion-dependency-review

Run the fusion-dependency-review workflow for this PR:

Research upstream changes and existing PR discussion.
Assess security, code quality, and impact.
Post a research comment using assets/research-comment-template.md.
Produce a confidence score (high / medium / low) using the criteria in .github/instructions/dependabot-pr.instructions.md.

Keep research focused — do not deep-dive unless a concern surfaces.

Step 5 — Create changesets

Follow the changeset decision rules in .github/instructions/dependabot-pr.instructions.md. Create, commit, and push changesets for affected published packages.

Step 6 — Validate

pnpm test && pnpm build && pnpm -w check

On failure: attempt trivial fixes (e.g., pnpm format). If non-trivial, mark needs-manual-intervention.

Step 7 — Merge or report

High confidence:

Post verdict comment using assets/verdict-comment-template.md.
gh pr merge <number> --squash --admin

Medium or low confidence:

Post verdict comment with findings.
Do not merge. Include in final report.

Step 8 — Final batch report

PR	Title	Status	Confidence	Action
#N	...	merged / skipped / failed	high/med/low	merged / needs review / needs intervention

Expected output

Research and verdict comments posted to each processed PR
Changesets created where required
High-confidence PRs merged via admin squash
Final batch summary table
List of PRs needing manual intervention with reasons

Safety & constraints

This skill is mutation-capable. .github/instructions/dependabot-pr.instructions.md takes precedence on conflicts.

Never:

Merge without posting research and verdict comments first
Merge a PR with failing validation
Merge major version bumps without explicit user override
Merge the base branch into a Dependabot PR branch (rebase only)
Force-push without --force-with-lease
Process PRs without initial user confirmation

Always:

Return to main after batch processing is complete

custom-dependency-pr-solver

Dependency PR Solver

When to use

When not to use

Required inputs

Delegation

Instructions

Step 1 — List and triage

Step 2 — Process each PR sequentially

Step 3 — Checkout and rebase

Step 4 — Review via fusion-dependency-review

Step 5 — Create changesets

Step 6 — Validate

Step 7 — Merge or report

Step 8 — Final batch report

Expected output

Safety & constraints

이 저장소의 다른 Skills

이 저장소의 다른 Skills

Dependency PR Solver

When to use

When not to use

Required inputs

Delegation

Instructions

Step 1 — List and triage

Step 2 — Process each PR sequentially

Step 3 — Checkout and rebase

Step 4 — Review via fusion-dependency-review

Step 5 — Create changesets

Step 6 — Validate

Step 7 — Merge or report

Step 8 — Final batch report

Expected output

Safety & constraints