agentleFS
manastalukdarmanastalukdar/ai-devstudio/skills/contributing/SKILL.md

contributing

Skill1 starsChanged 7 months agoMITView on GitHub

Contribution readiness assessment analyzing project guidelines and requirements

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use e2e, worktree 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.
  • SentrySkill

    e2e

    Run E2E tests for Sentry JavaScript SDK test applications

    Also in 3 projects that use this

  • MicrosoftSkill

    worktree

    Create, reuse or clean up a dedicated git worktree for working on a pull request or a private branch. Use from any PR-scoped workflow that needs an isolated checkout to keep current code and build output untouched.

    Also in 3 projects that use this

  • NVIDIASkill

    testing

    Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 2

    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:

    Should this be one PR or multiple?

    line 29
  2. Distinctive:

    Do all tests pass?

    line 35

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

Complete Contribution Strategy - Context Aware

I'll analyze everything needed for your successful contribution based on your current context and work.

Strategic Thinking Process

<think> For a successful contribution, I need to analyze:
  1. Current Work Context
    • What has been done in this session?
    • Are we mid-implementation or post-completion?
    • What type of changes were made (feature, fix, refactor)?
    • Is the work ready for contribution?
  2. Project Type & Standards
    • Is this open source, company, or personal project?
    • What are the contribution guidelines?
    • Are there specific workflows to follow?
    • What quality gates exist (tests, lint, reviews)?
  3. Contribution Strategy
    • Should this be one PR or multiple?
    • Which issues does this work address?
    • What documentation needs updating?
    • Who should review this?
  4. Pre-flight Checklist
    • Do all tests pass?
    • Is the code properly formatted?
    • Are there any lint warnings?
    • Is documentation updated?
    • Are commits well-organized?</think>

Token Optimization

Expected range: 500–1,500 tokens (initial), 100 tokens (cache hit)

Caching: Caches project structure in .claude/cache/understand/project_structure.json for 7 days.

Early exit: Returns immediately if CONTRIBUTING.md already exists and is current.

Patterns used: Grep-before-Read, early exit, template-based generation, caching

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.

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.