leocaseiro / leocaseiro/notation-hero

List of WIP worktrees:

Open
#142 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
1d 11h
Merged PRs (30d)
8

Description

List of WIP worktrees preserved on 2026-07-15 (session: docs-confusion-review).

These 5 worktrees had 7–15 uncommitted files sitting for weeks — surfaced during the docs-cleanup triage as the "ADHD fingerprint" of start-many-finish-few. Preserved as WIP branches before the Tier 1 + Tier 2 worktree prune. Each branch has one chore(wip) commit on top of the branch's original HEAD.

The 5 branches

# Branch Files Delta
1 claude/admiring-ramanujan-c06910 13 +139 / -52
2 claude/intelligent-goldstine-9eeb15 13 +139 / -52
3 claude/nostalgic-elbakyan-6fdd4b 13 +139 / -52
4 claude/youthful-blackburn-2a40d6 15 +244 / -70
5 claude/pensive-boyd-6d17e3 7 +127 / -40

Notes

  • Duplicates likely: Branches 1–3 have IDENTICAL diff stats and were likely a shared exploration cloned across 3 sessions. Consider keeping one and marking the other two as duplicates when you review.
  • Modified files pattern (all 5): mostly SUPERSEDED root docs (feature-freeze.md, handoff.md, handoff-prompts.md, design-stack.md, player-app-ui.md, scope.md, stack-brainstorm.md) plus docs/mockups/*.html. Review each to decide if the modifications are worth extracting into a proper PR.
  • .specstory tool files are included in each commit (not in the worktree's base .gitignore at those old commit points); ignore them when reviewing.
  • Per the "never delete remote branches" rule, these branches stay on GitHub regardless of your decision — this issue is the index.

Session that surfaced this

docs-confusion-review, worktree clever-mendel-8e382c (branch claude/docs-confusion-review-ee6c2f), commit 42d3e54 on master.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the five linked branches and their listed diffs, reviewing the modified root documents and docs/mockups/*.html. Ignore the included .specstory files, and check the notes about identical stats for possible duplicates. Done means deciding whether any changes should be extracted into a proper PR and recording the review outcome while preserving the branches.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.