fix: update stale pylings references to pythonlings

[muhamedfazalps]

Problem

CLAUDE.md still references the old pylings command after the rename to pythonlings in 0.3.0.

Fix

Updated all stale pylings references to pythonlings in CLAUDE.md.

Fixes #24

If this fix helped you, consider buying me a coffee: https://buymeacoffee.com/muhamedfazalps

Summary by CodeRabbit

• Documentation
  • Standardized developer documentation across all guidance sections, updating naming conventions and command examples used in installation, testing, verification, and operational workflows.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 528b0ac7-062e-4910-b9cb-7b0475a40715

📥 Commits

Reviewing files that changed from the base of the PR and between 10e6bb0 and 44a29f5.

📒 Files selected for processing (1)

• CLAUDE.md

📜 Recent review details

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: CR
Repo: abhiksark/pythonlings

Timestamp: 2026-06-20T06:16:48.697Z
Learning: Keep UI behavior in screens/widgets and behavior logic in core to maintain testability separation

Learnt from: CR
Repo: abhiksark/pythonlings

Timestamp: 2026-06-20T06:16:48.697Z
Learning: Ensure each exercise triple (exercise source, checks, solution, and info.toml entry) stays in sync when changing curriculum

Learnt from: CR
Repo: abhiksark/pythonlings

Timestamp: 2026-06-20T06:16:48.697Z
Learning: Run async tests under `pytest-asyncio` in auto mode

Learnt from: CR
Repo: abhiksark/pythonlings

Timestamp: 2026-06-20T06:16:48.697Z
Learning: Use conventional commit prefixes (`feat:`, `fix:`, `docs:`, `chore:`) and work flows through `feature/*` → `dev` → `main`

---

📝 Walkthrough

Walkthrough

CLAUDE.md is updated to replace all pylings references with pythonlings across CLI examples, package paths, and the learner workspace state directory (.pylings/state.json → .pythonlings/state.json). The Conventions section is reformatted as a bullet list with unchanged content.

Changes

CLAUDE.md pylings → pythonlings rename

Layer / File(s)	Summary
CLAUDE.md full rename and reformat CLAUDE.md	All CLI examples updated to pythonlings (including a new pip install -e ".[dev]" step); architecture paths updated from pylings/ to pythonlings/ and workspace state dir renamed to <workspace>/.pythonlings/state.json; layering bullets use pythonlings/ paths; conventions section reformatted as bullets.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 The old name pylings has been swept away,
Now pythonlings leads us each step of the day.
The docs were confused, but confusion has fled,
With .pythonlings/state.json ahead!
Hop along, coder — the path is now clear. 🥕

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description clearly explains the problem and fix, and references issue #24, but does not follow the provided template structure with Summary, Tests, Screenshots, and Checklist sections.	Restructure the description to match the template: add a Summary section, Tests section, Screenshots section, and complete the Checklist with required items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly addresses the main change: updating outdated pylings references to pythonlings in CLAUDE.md, which is the core objective.
Linked Issues check	✅ Passed	The PR successfully updates all stale pylings references to pythonlings throughout CLAUDE.md, addressing both the stale documentation and PyPI name collision issues raised in #24.
Out of Scope Changes check	✅ Passed	All changes in the PR are directly related to updating CLAUDE.md documentation from pylings to pythonlings as required by issue #24; no out-of-scope modifications are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[abhiksark]

Thanks so much for jumping on this so fast, @muhamedfazalps — you read #24 exactly right: CLAUDE.md was the one spot still pointing at the old pylings command after the rename. 🙌

Unlucky timing on my side: the same fix went out in v0.3.1 just before this could land (#26), so #24 is already closed and main now conflicts with this branch. That's purely a crossover — your diagnosis was spot on.

Two small things worth keeping for next time (both easy traps):

1. One line should stay pylings. The blanket pylings → pythonlings replace also rewrote this line — "the unrelated pylings PyPI name belongs to a different project" — which intentionally refers to a different project on PyPI, so it needs to keep the old name. A targeted replace (or eyeballing each hit) avoids clobbering it.
2. The diff is +61/−61 for ~7 real changes — looks like the file's line endings flipped to CRLF on save, so every line shows as modified. git config core.autocrlf input (or an .gitattributes with * text=auto) keeps future diffs to just the lines you actually touched.

Closing this since it's already on main, but I'd genuinely love to have you back — I just shipped v0.4.0 (zero-config onboarding) and there's plenty more to do. Happy to point you at a few good-first-issues if you're up for it. Thanks again for caring enough to send a fix! 🚀