Add practical Weave Git merge skill - #80
Draft
leynos wants to merge 1 commit into
Draft
Conversation
Document the driver's real per-file contract, entity resolution pipeline, fallback boundaries, exit statuses, and safe rebase inspection workflow. Include discoverable skill metadata and a detailed behavioural reference so agents can diagnose Weave results from code-backed mechanics rather than the limited user documentation alone.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
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
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.
Summary
This branch adds a practical Weave Git merge skill so agents can configure,
inspect and troubleshoot the driver from its actual implementation rather
than relying on the project's limited user documentation.
The guidance explains Git's per-file driver contract, Weave's entity-level
resolution pipeline, fallback boundaries, exit statuses and safe inspection
during merges and rebases.
Review walkthrough
Validation
git diff --check origin/main...HEAD: passed.make all: formatting, lint, type checking and all 187 tests passed. The repository-wide spelling step remains red only for pre-existing findings in unrelated skills; the newweave-git-mergeskill has no spelling findings.Notes
The skill was derived from the Weave driver, setup command, merge engine,
fallback implementation and integration tests in the local Weave checkout.