agentleFS
Sign inStart free
DevolutionsDevolutions/IronRDP/.agents/skills/contribute/SKILL.md

contribute

Skill3.3k starsChanged 2 days agoApache-2.0View on GitHub

Pick the delivery flow by scale - a test-first fix in place, one led pull request, or an orchestrated multi-pull-request effort - and where the intent, contract, test, and review skills enter. Use at the start of any non-trivial change, or when asked how to approach or stage work.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Every flow is the same loop at a different scale: decide what must hold, write the check that fails without it, make it pass, and have …

    line 6

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

Every flow is the same loop at a different scale: decide what must hold, write the check that fails without it, make it pass, and have someone who did not write it review.

Pick the smallest flow that fits

FlowWhenRun
FixOne behaviour at one seam; every decision it needs is already in the intent, the contract, or the bug reporttdd here, then code-review
ChangeOne pull request; may raise a design decision or need more than one pair of handsgrill-intent for any decision none of those states, then lead
EffortSeveral pull requests, a second party that must agree on an interface, or a suite written blindorchestrate-effort

Promote when a signal appears rather than starting big, because each tier adds sessions and context to keep in step. A decision neither the intent, the contract, nor the report states promotes to Change: stop and run grill-intent rather than settling it in a test or code, since the first place a decision lands becomes the text everything else is bent to. A second party or a CONTRACT.md change promotes to Effort: the contract is its own pull request before the code that realises it.

Where the other skills enter

  • intent-files: read every applicable intent file before the first edit, in every flow.
  • contract-authoring and contract-review: when two independently built parties must agree; the contract precedes its first implementation.
  • blind-testsuite: when a wrong expected value would be invisible to the implementer, as in cryptography, codecs, and wire protocols; written from the contract before any implementation.
  • test-writer for every test, test-reviewer and test-oracle-reviewer through code-review, dependency-reviewer through code-review when a manifest or lockfile changes, and dependency-pruner then test-pruner on the diff once the code and tests are complete and before the last review.
  • intent-drift-audit: once a realisation is claimed complete, in the lead's final check or the reviewer's pass, never mid-implementation.
  • variants: when a named design choice needs implementation evidence rather than a paper answer.
  • review-feedback-loop: once a pull request has findings.

Wrong-flow signals

  • An expected value you cannot justify independently of the code under test: the oracle, perhaps the seam, is wrong; see test-oracle-reviewer.
  • An intent file, CONTRACT.md, or blind suite this pull request does not own edited inside it: that change belongs to the pull request that owns the text.
  • More open pull requests than you can verify one by one: stop opening new ones.

Download now (ZIP)

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 1 mentionJul 2026: 16 mentionsAug 2026: 1 mentionSep 2026: 15 mentionsOct 2026: 14 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Devolutions/IronRDP repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about Devolutions/IronRDP

The biggest 5 of 60 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 60

Talked about on GitHub, Bluesky and Hacker News (60 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 9

4 more on Bluesky

On Hacker News · 1

Does it work?

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

Reviews can't be read right now.

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