agentleFS
Sign inStart free
rubycatcorubycatco/claude-agent-sdk-ruby/.claude/skills/port-python-parity/SKILL.md

port-python-parity

Skill51 starsChanged 33 days agoMITView on GitHub

Port features from the official Python claude-agent-sdk to this Ruby gem for parity. Use when syncing with a new Python SDK release, running a gap analysis, or batching parity fixes.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. ya-luotao/claude-agent-sdk-ruby★ 51100% same

    Edited · 0

    None found.

    Wrote their own version · 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 repository2 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:

    When citing a fact about this gem (dependency bounds, config defaults, API shape), verify it against the code (gemspec, lib/) — not against …

    line 14

≈ “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

Port Python SDK changes to this Ruby gem. Target version(s): $ARGUMENTS (if empty, find the latest unported Python version via gap analysis below).

Source of truth

  • Python SDK checkout: ../claude-agent-sdk-python (relative to this repo). Pull latest before starting.
  • Repo-local parity record (primary, always available): the README parity comparison table and CHANGELOG.md — update both whenever a feature lands.
  • Auto-memory files project_porting_pattern.md and project_parity_gaps.md hold the last-checked version and history (supplementary — they may be absent in fresh environments; if missing, derive the last ported version from CHANGELOG.md instead).
  • When citing a fact about this gem (dependency bounds, config defaults, API shape), verify it against the code (gemspec, lib/) — not against CLAUDE.md, README prose, or memory, which can lag the code.

Workflow

  1. Gap analysis — diff the Python SDK between the last ported version and the target: read its CHANGELOG.md and git log for the range. Verify the version tags actually exist first (git tag -l) — Python's versioning has jumped ranges before (v0.1.81 → v0.2.82). List each change as port / adapt / skip (Ruby-N/A), with the Python PR number.
    • Don't classify a PR by its label — read its full diff. A PR that looks Ruby-N/A on the surface (asyncio/anyio plumbing, CI changes, type annotations) often carries embedded behavioral changes that DO apply: e.g., Python #990 was "trio compatibility" but also simplified flush() semantics and narrowed exception swallowing. For each skip verdict, enumerate the semantic changes inside the diff and confirm each one is already matched (or genuinely N/A) in the Ruby counterpart files, citing file:line.
  2. Branch — feature/sync-python-sdk-<python-version> (e.g., feature/sync-python-sdk-0.1.56). Batch-style audit work uses audit/<topic>-batch-<n> instead.
  3. Port — adapt Python idioms to Ruby conventions:
    • snake_case names, keyword args, plain classes with attr_accessor (no Struct/Data)
    • to_h serialization with camelCase keys for CLI compatibility
    • user-facing callbacks must go through FiberBoundary.invoke
    • RSpec expect syntax only; add specs mirroring the Python tests
  4. Commit messages — reference the Python PR number, e.g. Add local-disk list_subagents (Python #825).
  5. Verify — bundle exec rake (spec + rubocop) must be green. Run RUN_INTEGRATION=1 bundle exec rspec if the change touches the CLI wire protocol.
  6. PR — title references the Python SDK version; body lists each ported change with its Python PR number.
  7. Record — update the README parity table, CHANGELOG.md, and the memory files (new "last ported" version, anything skipped and why).

Known traps from past batches

  • The mcp gem's API has shifted between minor versions — verify against the locked version, not docs.
  • Enumerator-based streaming input crosses threads; watch for FiberError (see fiber_boundary.rb docs).
  • Some Python features are CLI-version-gated — prefer version-independent detection (in-band errors over version sniffing).

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