Repository navigation
Conversation
This was referenced Aug 29, 2026
Pepps233
force-pushed
the
feat/evolved-skill-memory-relationship
branch
2 times, most recently
from
August 30, 2026 15:10
e3538bb to
c73beff
Compare
Pepps233
force-pushed
the
feat/evolved-skill-memory-relationship
branch
from
August 30, 2026 21:32
c73beff to
f3de832
Compare
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
Define and enforce the relationship between evolved skills and
EVOLVE.mdso reusable procedural workflows move into skills while complementary behavioral constraints remain in memory, and any later removal or replacement of procedural memory requires an explicit proposal.Reasoning
Ordered setup, tool, debugging, recovery, and verification routines should be retrieved as skills instead of consuming every prompt. Broad behavioral constraints can remain useful alongside those procedures, so activation cannot infer that related memory is safe to delete.
The Skill Curator now receives explicit separation and relationship semantics. The writer then reloads the immutable source candidates, verifies the relationship digest accepted by deterministic validation, and binds the resulting disposition into the mutation batch. Complementary and independent guidance remains unchanged, fallback or superseded guidance records that an explicit memory proposal is required, and conflicting or fully redundant guidance cannot reach activation.
Changes
EVOLVE.mdduring skill activation and require a separate explicit proposal before fallback or superseded procedural memory can change.Stack
Position: 11 of 12
Base: #150
Next: #152
Testing
cd packages/evolution && node ../../node_modules/vitest/dist/cli.js --run test/skill-curator.test.ts test/skill-writer.test.ts test/filesystem-store.test.ts test/skill-candidate-registry.test.ts test/skill-evaluator.test.ts test/skill-draft-validator.test.tsnpm run check(blocked by the pre-existing model-catalog TypeScript failures also reported on feat(agent): observe evolved skill lifecycle outcomes #150; nopackages/evolutionerrors)This pull request is AI-generated by Diffex.