NexRL
CLAUDE.md119 starsChanged 8 months agoApache-2.0View on GitHub
NexRL is an ultra-loosely-coupled LLM post-training (reinforcement learning) framework by Nex-AGI Team. Python 3.12+, Apache 2.0 licensed. Always read and follow the instructions in .ai-instructions/ first: - .ai-instructions/developing/documentation.md — Documentation-first workflow - .ai-instructions/developing/testing-and-examples.md — Testing policy (tests in tests/ only, no ad-hoc examples) - .ai-instructions/developing/commit-guidelines.md — Commit message format, no AI co-author - .ai-instructions/code-review/generic.md — Pre-commit review checklist Available Claude skills in .claude/skills/: - fix-issue — Worktree-based GitHub issue fixing - github-pr — PR creation from worktree branches - git-commit…
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 75
Always update docs: when changing documented behavior
≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claude Code Instructions for NexRL
Project Overview
NexRL is an ultra-loosely-coupled LLM post-training (reinforcement learning) framework by Nex-AGI Team. Python 3.12+, Apache 2.0 licensed.
Existing Guidelines
Always read and follow the instructions in .ai-instructions/ first:
.ai-instructions/developing/documentation.md— Documentation-first workflow.ai-instructions/developing/testing-and-examples.md— Testing policy (tests intests/only, no ad-hoc examples).ai-instructions/developing/commit-guidelines.md— Commit message format, no AI co-author.ai-instructions/code-review/generic.md— Pre-commit review checklist
Project Structure
nexrl/ # Main package (algorithm, agent, trainer, rollout_worker, etc.)
cli/ # CLI tools
tests/ # Tests (unittests/, lint/)
recipe/ # Training recipes
scripts/ # Utility scripts
docs/ # Documentation (developer-guide/)
docker/ # Docker configsBuild & Tooling
- Package manager: setuptools (see
pyproject.toml) - Formatter: black (Python 3.12), isort
- Linter: pylint (
.pylintrc), mypy - Tests: pytest (
pytest.ini—tests/dir,-v --tb=short --strict-markers) - Pre-commit:
.pre-commit-config.yaml(black, isort, license header, pylint, mypy)
Key Commands
# Run tests
python -m pytest tests/ -v
# Run specific test
python -m pytest tests/unittests/test_foo.py -v
# Lint
python -m pylint nexrl/ --rcfile=.pylintrc -rn -sn
python -m mypy nexrl/ --ignore-missing-imports
# Format
python -m black nexrl/ tests/
python -m isort nexrl/ tests/
# License header fix
python tests/lint/fix_license_header.py <files>Skills
Available Claude skills in .claude/skills/:
- fix-issue — Worktree-based GitHub issue fixing
- github-pr — PR creation from worktree branches
- git-commit — Commit workflow with linting/testing
- code-review — Python code review
- testing — pytest and linting
- address-pr-comments — Handle PR review comments
Agents
.claude/agents/code-review/AGENT.md— Automated code review.claude/agents/testing/AGENT.md— Automated testing
Rules
- Never add AI co-author lines to commits
- Never create example/test files outside
tests/unless asked - Always update docs when changing documented behavior
- Follow documentation-first approach — read docs before coding
- Use git worktree for all issue work (multi-agent isolation)
- License headers required on Python, shell, YAML, TOML files
In this repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- address-pr-commentsSkill
- code-reviewSkill
- fix-issueSkill
- git-commitSkill
- github-prSkill
- testingSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

