agentleFS
Sign inStart free
Yeachan-HeoYeachan-Heo/oh-my-claudecode/skills/why/SKILL.md

why

Skill41k starsChanged 5 days agoMITView on GitHub

Investigate why code is the way it is from evidence — human rulings verbatim, git archaeology, linked issues, incident records — every claim labeled evidence, inference, or guess. For 'why was this built this way'.

112 other projects use a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 2 mentionsMar 2026: 17 mentionsApr 2026: 3 mentionsMay 2026: 7 mentionsJun 2026: 0 mentionsJul 2026: 2 mentionsAug 2026: 1 mentionSep 2026: 1 mentionOct 2026: 32 mentionsNov 2026: 19 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Yeachan-Heo/oh-my-claudecode repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Yeachan-Heo/oh-my-claudecode

The biggest 5 of 84 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 84

Talked about on GitHub, YouTube, Bluesky and the web (84 times).

On GitHub · 50

45 more on GitHub

On YouTube · 20

15 more on YouTube

On Bluesky · 10

5 more on Bluesky

On the web · 4

Used with

Projects with it also use addskill, apply-firmware and 10 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.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 105 edited versions we read keep these.

  • 3

    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:

    Incident and observability sources: When configured, query them through their own tools (Sentry, Datadog, Databricks, dashboards, incident …

    line 40
  2. Distinctive:

    Write the answer with three labeled tiers — evidence (cited),

    line 53
  3. Distinctive:

    Every claim about a past decision names its source in the same sentence.

    line 59

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

Why

Answer "why is it like this?" from evidence, not vibes. The deliverable is a cited answer, not a fix; a fix that falls out of the answer goes through its own lane.

When to use

  • "why was this built this way", "why does this exist"
  • "are we sure about Z" before betting work on Z
  • "should we do X or Y" where the answer lives in history, not preference

Sources, in order of authority

  1. Human rulings. A decision a person made is quoted verbatim with attribution (commit message, issue comment, PR review, chat log). Never paraphrase a ruling into your own words; label agent interpretations as interpretations, and missing originals as missing. A copy of a ruling is not a new decision.
  2. Code archaeology. git log --follow, git log -S, blame on the deciding lines, and the diff that introduced them. Name the commit and what problem its message claims to solve.
  3. Linked records. Issues and PRs reachable from the code (references in commit messages, gh issue list --state all --search, PR review threads) — acceptance criteria and rejected alternatives live here.
  4. Incident and observability sources. When configured, query them through their own tools (Sentry, Datadog, Databricks, dashboards, incident postmortems) or MCP servers (Slack, Linear, Notion). Cite the alert, thread, ticket, or postmortem. If a source needs credentials you do not have, say so and move on.

Method

  1. State the question and what would count as an answer.
  2. Fan out source gathering to a read-only subagent when the history is long (oh-my-claudecode:explore); keep synthesis in the lead.
  3. Reconcile: where sources conflict, the more authoritative source wins, and the conflict itself is reported.
  4. Write the answer with three labeled tiers — evidence (cited), inference (your reasoning from evidence, marked), guess (marked). End with the one action the answer most supports, or "no action".

Rules

  • Every claim about a past decision names its source in the same sentence.
  • Absence of evidence is reported as "no record found", never as "no reason".
  • The answer never edits code. If the user asks to act on it, hand off to execute or debug.

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