Ext Ops Panel
Open dashboard
Comparison

cycle vs pipeline

pipeline is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.

cycle is a plugin bundle for AI coding tools published by George-RD. Marketplaces we read that list it: 1 (Community GitHub marketplaces). pipeline is a plugin bundle for AI coding tools published by Haytham Zahran. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacecyclepipeline
Community marketplace george-rd/claude-next-level Not seen in the last pass
Version: 2.0.0
Forks (GitHub): 1
Stars (GitHub): 13
Not marked · First seen
Not listed
Community marketplace h-zahran/delivery-kit Not listed Removed on 2026-10-22
Version: 1.6.2
Forks (GitHub): 1
Stars (GitHub): 7
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

cycle vs pipeline
Factcyclepipelineno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)137
Forks (GitHub)11
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)25
Licence (differs)Not statedMIT
Repository (differs)github.com/george-rd/claude-next-levelgithub.com/h-zahran/delivery-kit
Changes in the last 7 days (differs)02
First seen (differs)2026-10-192026-10-20

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of pipeline

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • pull-request

    Pull request workflows: create, update, babysit CI, and reviewer follow-up

    by Ben Drucker · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • git

    Git workflow automation (commit, PR, branching, changelog)

    by Arkhe · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • git-pr-workflows

    Git workflow automation, pull request enhancement, and team onboarding processes

    by Seth Hobson · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • git-pr-workflows

    Git workflow automation, pull request enhancement, and team onboarding processes

    by Seth Hobson · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Git

    Conventional Git automation, advanced repository management, and GitFlow workflow automation for feature, hotfix, and release branches with post-finish cleanup

    by Frad LEE · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • harness-init

    Makes a repo agent-ready with AGENTS.md, boundary tests, CI pipeline, and GC scripts based on OpenAI's harness engineering methodology

    by Gizele1 · Plugin bundle

    Listed on: Claude Code: claude-plugins-community, Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

cycle

In its own words, on Community GitHub marketplaces:

Unified PR review system: /cycle:pr shepherds one or many PRs through review with dispatch-and-poll fix agents, worktree management, and CodeRabbit patterns.

pipeline

In its own words, on Community GitHub marketplaces:

Takes one feature from idea to reviewed pull request — spec, plan, build, review, ship — stopping to ask you at every step that leaves your machine. Requires spec-kit in the target repository.

How to run each

cycle As a Claude Code plugin

Claude Code
/plugin marketplace add george-rd/claude-next-level
/plugin install cycle@claude-next-level

pipeline

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: cycle · What it can do: pipeline · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built