Forward-merge release/1.7 into develop#1973
Merged
Merged
Conversation
…1970) - Require agents to read `skills/skill-evolution/SKILL.md` before creating, editing, or deciding whether to update files under `skills/` - Strengthen the `skill-evolution` trigger wording so skill maintenance tasks route there before editing the target skill ## Motivation Tests showed that agents could jump directly to editing a named target skill, such as `nat-telemetry`, without first consulting `skill-evolution`. This change makes `skill-evolution` an explicit pre-edit gate for skill maintenance tasks. ## By Submitting this PR I confirm: - I am familiar with the [Contributing Guidelines](https://github.com/NVIDIA/NeMo-Agent-Toolkit/blob/develop/docs/source/resources/contributing/index.md). - We require that all contributors "sign-off" on their commits. This certifies that the contribution is your original work, or you have rights to submit it under the same license, or a compatible license. - Any contribution which contains commits that are not Signed-Off will not be accepted. - When the PR is ready for review, new or existing tests cover these changes. - When the PR is ready for review, the documentation is up to date with these changes. ## Summary by CodeRabbit * **Documentation** * Added a “Skill Evolution” prerequisite: contributors must read the Skill Evolution guidance before creating, editing, or deciding on skill updates. * Revised the Skill Evolution guidance to frame using the resource prior to any skill changes and to streamline the workflow with recommendations for minimal, targeted edits. [](https://app.coderabbit.ai/change-stack/NVIDIA/NeMo-Agent-Toolkit/pull/1970?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack) Authors: - Yuchen Zhang (https://github.com/yczhang-nv) Approvers: - Will Killian (https://github.com/willkill07) URL: #1970
](https://app.coderabbit.ai/change-stack/NVIDIA/NeMo-Agent-Toolkit/pull/1970?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack){kind=link}
Author
|
SUCCESS - forward-merge complete. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Forward-merge triggered by push to release/1.7 that creates a PR to keep develop up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge. See forward-merger docs for more info.