docs: point contribution steps at the develop branch

AGENTS.md

@@ -47,7 +47,7 @@
 
 ## Commits and branches
 
-- Work on a feature branch; do not commit directly to `main`.
+- Work on a feature branch; do not commit directly to `develop`, `main`, or any `release/*` branch.
 - Keep commits focused and atomic.
 - Use an imperative, capitalized commit subject with no trailing period.
 - Inspect staged changes before committing.

docs/source/refs/contributing.rst

@@ -50,7 +50,7 @@ follow the following steps to contribute code:
 3. Create a new branch for your changes.
 4. Make your changes and commit them.
 5. Push your changes to your fork.
-6. Submit a pull request to the `main branch <https://github.com/isaac-sim/IsaacLab/compare>`__.
+6. Submit a pull request to the `develop branch <https://github.com/isaac-sim/IsaacLab/compare/develop...develop>`__.
 7. Ensure all the checks on the pull request template are performed.
 
 After sending a pull request, the maintainers will review your code and provide feedback.

skills/developer/pr-workflow/SKILL.md

@@ -26,7 +26,8 @@ Do not use this skill to bypass repository checks or to push to `origin`.
 7. Add package changelog fragments when `source/<package>/` code changes.
 8. Check whether `CONTRIBUTORS.md` needs an update for a new contributor.
 9. Draft a commit message in imperative mood with no AI attribution.
-10. Use the PR checklist in `.github/PULL_REQUEST_TEMPLATE.md`.
+10. Confirm the pull request targets the `develop` branch. `main` and `release/*` are not contribution targets.
+11. Use the PR checklist in `.github/PULL_REQUEST_TEMPLATE.md`.
 
 ## Validation