agentleFS
prygrnprygrn/agent-kernel/skills/integrator/SKILL.md

integrator

Skill0 starsChanged 3 months agoMITView on GitHub

Use this role when the agent must reconcile work developed in parallel — lots of one feature, or features that converge — into a semantically consistent whole before merge, or report decisions taken from a source repository into another repository without writing into the source.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read each side's decisions and reconcile cross-lot inconsistencies into one consistent result, before the merge into the integration branch.

    line 37
  2. Distinctive:

    Prefer an alignment commit on the development branch, before the merge, so the merge itself carries no code change.

    line 47
  3. Distinctive:

    When no intermediate state passes the hooks — the fix only compiles or lints once both sides are combined — put the fix in the merge commit …

    line 49
  4. Distinctive:

    Never bypass a hook to get an integration through.

    line 52
  5. Distinctive:

    Read the source repository to carry its actual decisions into the target repository — the source's product spec is authoritative, its …

    line 57
  6. Distinctive:

    Write only in the target repository.

    line 59
  7. Distinctive:

    When a substantive change (not a typo) is made, state it plainly in the review so any downstream version bump or follow-up can be triggered …

    line 62
  8. Distinctive:

    Never write to the feature contract or specs.

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Integrator

PRODUCES:       a semantically-consistent integration — either parallel work reconciled
                 before merge (cross-lot decisions made compatible), or a target
                 repository updated to reflect a source repository's decisions
NEVER PRODUCES: feature contract changes, spec changes, new feature behavior beyond what
                 the lots already implement, any write into a read-only source repository
DEPENDS ON:     rules/always/methodology.md (contract or tests as the reference;
                 normative hierarchy; read-before-acting; flag-undecided-questions;
                 verify external dependencies against their real source)
                 rules/always/testing.md (tests are never weakened to make an
                 integration pass)
                 rules/always/git.md (branch/review conventions; an agent may merge the
                 main branch into its own branch, only the human merges into main; hooks
                 are never bypassed)
PERMISSIONS:
  source code      : W        # in the target repo only; never in a read-only source repo
  tests            : W        # in the target repo only
  feature contract : R
  specs            : R
  journal          : W        # when one exists: logs non-trivial integration decisions
  review           : W

Two modes

Mode A — reconcile parallel work (before merge)

  • Applies when work was developed in parallel: lots of one feature, or separate features that converge on the same branch. It does not run on a single isolated change.
  • Read each side's decisions and reconcile cross-lot inconsistencies into one consistent result, before the merge into the integration branch. Inconsistencies are not only in code — units, null vs empty object, which lot owns a shared concern such as auth — but also in toolchain and minimum language version, dependencies, and lint configuration. A clean git merge proves none of this.
  • The reconciliation must satisfy the feature contract when one exists, and every side's tests, passing together once combined. Never edit the contract or weaken a test to justify a reconciliation choice.
  • Where lots share an interface, verify both sides honor the same signature — the one the contract freezes when one exists; a clean git merge does not prove semantic agreement.
  • Prefer an alignment commit on the development branch, before the merge, so the merge itself carries no code change.
  • When no intermediate state passes the hooks — the fix only compiles or lints once both sides are combined — put the fix in the merge commit itself and explain it in the commit message and the review.
  • Never bypass a hook to get an integration through; if no state can pass, stop and report the options to the human.

Mode B — cross-repo reporting (read-only source)

  • Read the source repository to carry its actual decisions into the target repository — the source's product spec is authoritative, its journal gives the chronology.
  • Write only in the target repository. Never write into the source, not even a trivial fix spotted in passing; flag it for the human instead.
  • Stay strictly within the target repository's scope; touch only the sections the task names.
  • When a substantive change (not a typo) is made, state it plainly in the review so any downstream version bump or follow-up can be triggered by the human.

Boundary

Never write to the feature contract or specs. The contract is the standard integration must satisfy, not a thing to adjust. In cross-repo work, the source repository is read-only without exception.

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.