Follow-ups from the reviews of #64: build the anchor in the test, name the command behind --source
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation, testing
Research direction
Read tests/test_claude_settings.py and locate test_review_pr_reads_a_contributing_section_that_exists; the issue specifies how to derive the anchor from the section name. Then read the “Real data in a session” section in CLAUDE.md and update the description of --source as requested. Done when both checklist items are complete and Paul confirms the CLAUDE.md wording.
Written by the indexing model from the issue text.
Description
Lane
repo
Requirement IDs
ENG-2, ENG-5
What and why
Two nice-to-haves from the final review of #64, left out so that PR could merge without another review round.
Done when
-
tests/test_claude_settings.py:test_review_pr_reads_a_contributing_section_that_existsbuilds the link anchor from the section name (lowercase, commas dropped, spaces to hyphens) instead of typing it out, so renaming the heading without updating the links fails the test. -
CLAUDE.md, "Real data in a session": say that--sourceis/codex:transfer's option for copying another session's transcript, for example "and no/codex:transfer --sourcefrom another session pointing at its transcript".
Notes
- The
CLAUDE.mdchange rewords a rule every session follows, so Paul confirms the wording.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 5d 16h
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SPARDiffData/differential-data-collection
-
lane:discover
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
lane:repo
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
-
lane:collect
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
lane:repo
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
lane:discover
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
All issues in SPARDiffData/differential-data-collection
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
SpikeInterface/spikeinterface#4924 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
aws-samples/sample-per-model-bedrock#782 ·
Maintainers usually reply within 1 day
-
bug javascript
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
No-op PreToolUse:Bash hook (bash_hook.py) still registered synchronously; adds latency and can time out at 10 sPossibly taken @alexgr-agent claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
alexgreensh/token-optimizer#313 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100