agentleFS
Sign inStart free
OlliTapioOlliTapio/claude_skills/skills/finalize/SKILL.md

finalize

Skill0 starsChanged 17 days agoMITView on GitHub

Create a PR, review it, fix issues, and auto-merge squash. Use when the user wants to ship changes end-to-end in one command — covers PR creation, self-review, fixes, and squash merge.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use simplify, debug and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Hugging FaceSkill

    simplify

    Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.

    Also in 3 projects that use this

  • AnthropicSkill

    debug

    Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    verify

    End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Create PR → review → fix → squash merge.

    line 8
  2. Very specific:

    Run the pr skill. Never add or ask for reviewers.

    line 12
  3. Very specific:

    If gh pr view --json reviewDecision -q .reviewDecision returns REVIEW_REQUIRED, stop after Step 3: report the PR URL and that it needs the …

    line 14
  4. Very specific:

    Do not request a review from anyone, and do not merge.

    line 16
  5. Very specific:

    Run the pr-review skill on the created PR.

    line 22
  6. Distinctive:

    If pr-review reports any P0/P1 still open, stop: report them with the PR URL.

    line 26
  7. Distinctive:

    If CI fails, fix and retry.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Finalize

Create PR → review → fix → squash merge.

Step 1: Create PR

Run the pr skill. Never add or ask for reviewers.

If gh pr view --json reviewDecision -q .reviewDecision returns REVIEW_REQUIRED, stop after Step 3: report the PR URL and that it needs the user's manual review. Do not request a review from anyone, and do not merge. Once the user says their manual review is done, ask who should review, add them with gh pr edit --add-reviewer, then continue from Step 4.

Step 2: Review PR

Run the pr-review skill on the created PR.

Step 3: Check open findings

If pr-review reports any P0/P1 still open, stop: report them with the PR URL. Do not merge. P2s are non-blocking — proceed.

Step 4: Wait for CI

gh pr checks --watch --fail-fast

If CI fails, fix and retry. Max 3 attempts.

Step 5: Squash merge

PR_NUMBER=$(gh pr view --json number -q .number)
PR_TITLE=$(gh pr view --json title -q .title)
gh pr merge "$PR_NUMBER" --squash --subject "$PR_TITLE" --delete-branch

Report the merged PR URL.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free