oliver-zehentleitner/

keep-the-why

GitHub Website

Keep the Why: a repo-native convention and agent skill that preserves the reasoning behind a codebase as a byproduct of working with your agent — so it stops re-suggesting rejected approaches, gives better answers, speeds up onboarding, and makes legacy projects tractable again.

141stars

13forks

4issues

MITlicense

2026since

Star historydaily snapshots by VibeCrowd

Collecting history — the radar snapshots this repo daily. The trend line appears after 3 days of data (1 so far).

Alternatives & relatedmatched by topic overlap

ComposioHQ/

awesome-claude-skills

▲ 585/wk

A curated list of awesome Claude Skills, resources, and tools for customizing Claude AI workflows

72k8.1kPython

sickn33/

agentic-awesome-skills

▲ 328/wk

AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,000+ agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.

44k6.5kPython

wshobson/

agents

▲ 148/wk

Multi-harness agentic plugin marketplace for Claude Code, Codex CLI, Cursor, OpenCode, GitHub Copilot, and Gemini CLI

38k4.1kPython

topoteretes/

cognee

▲ 254/wk

Cognee is the open-source AI memory platform for agents. Give your AI agents persistent long-term memory across sessions with a self-hosted knowledge graph engine.

30k2.9kPython

DietrichGebert/

ponytail

▲ 4.8k/wk

Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.

96k5.3kJavaScriptnew

Graphify-Labs/

graphify

▲ 4.6k/wk

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

102k9.9kPython

Comparekeep-the-why vs awesome-claude-skills keep-the-why vs agentic-awesome-skills keep-the-why vs agents

Agent skills inside · 1

All skills →

keep-the-whyPreserves or recovers the reasoning behind a codebase - architectural decisions, rejected alternatives, workarounds, incident learnings, operational constraints, and historical context the code itself cannot explain. Use when implementing or reviewing a non-trivial change involving a design decision, workaround, incident fix, operational constraint, rejected alternative, or changed assumption; when documenting an existing or legacy codebase; during onboarding or a maintainer handover; or when interviewing a developer before their knowledge is lost (e.g. before they leave or retire); or when thDesign & Presentation

SharePost on X LinkedIn