/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

affaan-m/everything-claude-code

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-29T22:12:31.688Z

3mo ago

affaan-m/everything-claude-code

A large, actively maintained open-source system for optimizing AI agent harness workflows. It packages agents, skills, hooks, commands, rules, MCP configs, and install tooling for Claude Code, Codex, Cursor, Opencode, and related environments. The repo is very popular and current, with 116,374 stars, 15,137 forks, and commits pushed on 2026-03-29.

Loading tags...

Stars116,374

Forks15,137

Default branchmain

Last pushed2026-03-29T13:06:45Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

6 of 6 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork if you want a note-first, planner-driven workflow and do not need the full upstream pace of updates. Stay with upstream if you want the broadest, most current multi-harness toolkit and lower merge risk.

Choose this fork if documentation language and presentation matter more than staying perfectly current. Choose upstream if you want the latest agent/workflow fixes and active maintenance.

Prefer the upstream project unless you specifically need a frozen copy. This fork has no visible product advantage and is 333 commits behind, so it is more likely to lag on compatibility and workflow fixes than to add value.

Choose upstream unless you specifically want this older snapshot. This fork does not show added capabilities, while its 522-commit lag means it likely trails current fixes and improvements.

Adopt this only if you specifically want a plain upstream mirror. For active use, upstream is the better choice because this fork adds nothing and is materially behind.

Choose upstream unless you specifically need a frozen, unmodified copy; this fork adds no clear capability and is significantly behind current upstream maintenance.

Fork comparison

inkdropapp/note-driven-agentic-coding-workflow

54/100

slowing

substantial

Choose this fork if you want a note-first, planner-driven workflow and do not need the full upstream pace of updates. Stay with upstream if you want the broadest, most current multi-harness toolkit and lower merge risk.

Likely purpose

To turn the upstream agent-harness toolkit into a note-driven coding workflow, with planner-oriented commands, rules, and agent guidance centered on capturing work in notes before execution.

Best for

People who want to drive coding tasks from notes and outlines.; Inkdrop users or teams using note-based project capture.; Adopters who prefer an opinionated planning workflow over a broad general-purpose harness bundle.

Additional features

Note-driven workflow guidance for turning notes into execution plans.
A dedicated planning command for structured task breakdown.
A planner agent tuned for note-based coordination.
A note-taking rule set that likely enforces capture-first or note-first habits.
Fork-specific documentation aimed at the Inkdrop workflow.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

It is 762 commits behind upstream, so it likely misses many recent upstream fixes, compatibility updates, and maintenance work.
It likely lags the broader upstream multi-platform harness support for Claude Code, Codex, Cursor, and Opencode.
It likely lacks or is behind upstream's larger install, repair, audit, and orchestration tooling.
It likely does not track the full upstream set of hooks, MCP configs, skills, and security workflows at current head.
Recent upstream improvements such as Codex compatibility and token-budget advisor fixes are probably not present here.
It trails upstream by 762 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Clearer opinionated workflow for users who want planning before coding.
Smaller, more focused surface area than the full upstream system.
Good fit for a note-centric personal or team process.

Risks

Heavy upstream lag makes future merges harder.
Narrower scope may mean less compatibility with the latest upstream harness features.
Users expecting the full Everything Claude Code experience may find this fork incomplete.