docs: add scoped agent instruction hierarchy - #59
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📜 Recent review details🧰 Additional context used📓 Path-based instructions (5)**/*📄 CodeRabbit inference engine (AGENTS.md)
Files:
{docs-site,pythonlings/docs}/**📄 CodeRabbit inference engine (CLAUDE.md)
Files:
docs-site/**📄 CodeRabbit inference engine (docs-site/AGENTS.md)
Files:
pythonlings/docs/**📄 CodeRabbit inference engine (pythonlings/docs/AGENTS.md)
Files:
pythonlings/docs/**/*📄 CodeRabbit inference engine (pythonlings/docs/AGENTS.md)
Files:
🧠 Learnings (1)📓 Common learnings🔇 Additional comments (4)
📝 WalkthroughWalkthroughThe repository replaces general guidance with a canonical ChangesContributor policy hierarchy
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: 🔵 Low · up to The change only reorganizes contributor guidance and does not alter application or release behavior. A bounded documentation follow-up remains to state the Python 3.9 CI gap and validation expectations; this is mergeable with maintainer awareness. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Summary
main, merge commits require green CI and resolved feedback, and merging requires explicit maintainer approvalCLAUDE.mdto a compatibility pointer to the canonical hierarchyWhy
The repository guidance was duplicated, partly stale, and did not capture the runtime, learner-state, curriculum, documentation-generation, security, release, and merge invariants that changes must preserve. This hierarchy keeps shared rules in one place and adds only directory-specific requirements locally.
The live repository uses
mainas its active integration branch;devcurrently has no unique commits and is behindmain. The policy therefore makes direct-to-mainpull requests explicit while retainingdevonly for an approved future release plan.This changes contributor and automation guidance only. It does not change application behavior, public APIs, curriculum content, or release configuration.
Validation
git diff --checkpython -m pytest -q(147 passed in 20.10s)pythonlings --root tests/fixtures/passing_curriculum verify(2 passed)mkdocs build --strict(passed; informational note that the local guide is not in site navigation)Confirmation item
pyproject.tomldeclares Python 3.9 support, while the current CI matrix covers Python 3.11 through 3.13. This PR records that gap without changing CI.Summary by CodeRabbit