skills.rest
noamr
noamrCOMMUNITY
Explore all skills by this author →
𝕏@nomsternomGitHub

Web Standards Archeologist (Paper Trail)

Trace web standards fragments to historical evidence sources in specification repositories.

18|2|Updated Mar 20, 2026
Search Tags:#git history#web standards#whatwg#spec archaeology#deep blame#browser bugs#issue tracing
One-click install
npx skills add https://github.com/noamr/web-archeologist --skill web-standards-archeologist-paper-trail
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Web Standards Archeologist (Paper Trail)
Source: https://github.com/noamr/web-archeologist/tree/main
Command: npx skills add https://github.com/noamr/web-archeologist --skill web-standards-archeologist-paper-trail

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standards engineers and AI agents often lack immediate historical context for explaining why a clause, fragment, or browser behavior exists in a specification, forcing manual digging through massive repositories, mailing lists, and issue trackers.

Core Features & Use Cases

  • Fragment discovery: Heuristics for ReSpec, Bikeshed, and CSS property IDs surface the canonical definition for a term or fragment across modern specifications.
  • Historical evidence: Deep blame workflows relying on git log -L, full repository history, and curated mappings back a line or algorithm to the commits and discussions that created it.
  • Discussion and call graph tracing: WebDex, Xref, issue trackers, and archived IRC/Matrix logs construct annotated call graphs and cite the rationale behind landing PRs, explainers, or normative edits.

Quick Start

Ask this skill to trace the historical origin of the HTML fragment or issue you are investigating.

Frequently Asked Questions about Web Standards Archeologist (Paper Trail)

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace the git history of a WHATWG or W3C spec fragment?▼

Trace spec fragments to historical roots using deep blame workflows with git log -L to surface commits and discussions that created the clause. It relies on full repository history and curated issue mappings to document the rationale behind the text.

Why does a specific browser bug or algorithm exist in a web standard?▼

Identifying why a browser bug or algorithm exists involves tracing the spec clause back to historical evidence sources. Curated issue trackers and archived IRC/Matrix logs construct annotated call graphs citing the rationale behind landing PRs and normative edits.

How do I find the canonical definition for a term across modern web specifications?▼

Finding the canonical definition for a term uses heuristics for ReSpec, Bikeshed, and CSS property IDs. Fragment discovery surfaces the exact definition across modern specifications by querying WebDex and Xref mappings.

Can I trace issues and discussions from WICG repositories back to normative edits?▼

Tracing WICG repository issues back to normative edits is supported by constructing annotated call graphs. It matches fragments, algorithms, or bugs with canonical definitions and references using curated issue and IRC logs.

What is the best way to document the rationale behind a specific HTML spec edit?▼

Documenting spec edit rationale requires matching fragments to historical evidence sources. Deep blame workflows and archived discussion logs trace the exact commits and conversations that landed the PR or explainer.

Does spec archaeology work with both Bikeshed and ReSpec formatting tools?▼

Spec archaeology supports both Bikeshed and ReSpec formatting tools. Heuristics for identifying Bikeshed definitions and ReSpec property IDs surface canonical definitions across modern specifications for accurate historical tracing.

Related Skills

Explore More Software Engineering Skills→
alastor0325alastor0325

spec-check

Validate web-exposed features against WHATWG/W3C specifications for WPT coverage.

Community
Advanced
hartphoenixhartphoenix
12

thischat

Locate active Claude Code session logs and stamp files with provenance metadata.

Community
Basic
berkcangumusisikberkcangumusisik
11

git-blame-explain

Explain code line origins using git blame and commit history.

Community
Intermediate
pcasarettopcasaretto

git-history-analyzer

Analyze git history to trace code evolution and identify contributors.

Community
Intermediate