agentleFS
Sign inStart free
Sagargupta16Sagargupta16/agent-brain/skills/oss/SKILL.md

oss

Skill2 starsChanged 11 days agoMITView on GitHub

Open-source router for the user's upstream work. Status of every open upstream PR with rebases of own-fork branches, fork cleanup once a fork's PRs are all merged or closed, vetting an idea against the 7/10 quality bar, finding contributions, and prepping a PR to the target repo's conventions. Use when the user says "open source", "OSS", "status of my open source", "rebase all open PRs", "delete this fork", "what maintainer asked", "is this worth contributing", "prep this PR for upstream", or runs /oss [status|vet|prep|find]. Never comments on an upstream PR without the user's explicit permission; find respects any contribution pause the user has recorded.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. sameerhimati/claude-code-kit★ 1same name
    2. csfh/skills★ 0same name

    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 repository16 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Never comment on upstream PRs without explicit permission.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

oss

One router for upstream contribution work. Pick the mode; read ONLY the matching reference, then follow it.

ModeTriggerReference
find"find contributions", hunt for issues matching skillsreferences/find-contributions.md
vet"is this worth a PR?", judge an idea against the 7+/10 barreferences/meaningful-oss-contribution.md
prep"prep upstream PR", match style/template before submittingreferences/upstream-pr-prep.md

Optional gate before find mode: if the user has recorded a contribution pause (brain recall oss pause), do NO new upstream PR hunting unless they explicitly ask in this session. vet and prep are always available for work the user initiates.

Standing rules (all modes):

  • Quality bar is 7+/10: real problems, live code paths, no self-promo list adds, no bundled fixes.
  • Trace the live entry point + read CONTRIBUTING for the base branch before writing anything. Patching a dead duplicate of the code, or targeting main when the project merges into dev, gets a PR closed.
  • Never comment on upstream PRs without explicit permission.

status mode and fork cleanup

Status and cleanup come up far more often than find or prep.

  • /oss status: list every open upstream PR authored by the user with age, last maintainer activity and CI state (gh search prs --author @me --state open), then rebase any own-fork branch that is behind (--force-with-lease on the fork branch only). Never comment upstream; a maintainer question is reported to the user, not answered.
  • Fork cleanup: a fork whose every PR is merged or closed (verify each with merged_at, both search and per-PR API) is deleted after backing up unmerged diffs to a local patch backup dir (for example ~/branch-backup/fork-patches/). Needs the delete_repo scope. Deleting the fork does not remove the PR record upstream.
  • A recorded contribution pause gates find only; status and cleanup are always allowed.

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