agentleFS
Sign inStart free
scolladonscolladon/craft/skills/integrate/SKILL.md

integrate

Skill2 starsChanged 34 days agoMITView on GitHub

Craft phase 11 - monitor CI to green, merge on user confirmation, clean up worktree/branch and repo tooling.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use discover, plan and 1 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.
  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • OpenAISkill

    audit

    Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Drift-baseline refresh offer: when the merged change touched skills/ or agents/ (the prompt surface whose economics the drift signal …

    line 42

“Common” is measured: kept by at least 6 in 10 of the 11 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

craft:integrate

Preamble (always runs — non-overridable)

  1. Manifest read (lint if standalone). Policy: merge-flags, non-blocking-jobs, scripts.pre-teardown from the manifest.

Procedure (default body — a manifest override: replaces everything below)

  1. Monitor CI → fix to green, ignoring jobs listed in non-blocking-jobs. Fixes land as conventional commits through the same gates as review fixes.

  2. Consult integrate action (see docs/contributing/specs/policy.md for surface semantics). Obey the returned surface:

    • ask (default, ADR-127) — ask the user to confirm the merge; on approval proceed, on decline record POLICY(ask:integrate→declined) and block.
    • never — refuse; record POLICY(never:integrate); phase no-ops.
    • always — proceed with no confirmation; record POLICY(always:integrate); no merge confirmation (ADR-128).

    Then invoke the VCS port integrate(prUrl) (see docs/contributing/specs/vcs.md); the adapter owns the host CLI. --squash / --delete-branch / merge-flags semantics live in the adapter binding. Always delete-branch: no merged branch lingers on the remote.

  3. Consult teardown, then tear the worktree down. Consult the teardown action separately before worktree teardown (per-verb granularity, ADR-126; see docs/contributing/specs/policy.md), append its POLICY(...) line, and:
    "${CRAFT_ROOT:-${CLAUDE_PLUGIN_ROOT}}/scripts/worktree-teardown.sh" <main-repo-dir> <worktree-path> \
  [--pre-teardown <manifest scripts.pre-teardown>]
    The script refuses while the validation run-lock is alive (dead-PID locks auto-clear; a live lock needs --force, which is recorded in the run record). The run ledger lives in the git common dir, not the worktree, so it outlives the teardown: Done derives the memory delta from it afterwards (docs/contributing/specs/run-record.md). The pre-teardown script is the matched pair of workspace-phase tooling activation — every activation gets its prune.
  4. Drift-baseline refresh offer: when the merged change touched skills/ or agents/ (the prompt surface whose economics the drift signal watches), offer the user a baseline refresh per skills/metrics/SKILL.md § Refreshing the committed baseline — the per-phase economics shifted on purpose, so the pre-change docs/contributing/metrics-baseline.report.json would flag the intended shift as drift forever. Declining is fine (the offer is advisory, like the signal itself); never refresh silently.
  5. Deliver the final summary (PR URL, what shipped, record). run-ledger.sh close does not run here: it is the last ledger action of the run skill's Done, after save and metrics have read the ledger.

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