Integrate knowledge graph context into SDLC lifecycle skills — Closes #158#159
Merged
conradbzura merged 1 commit intowool-labs:mainfrom Apr 6, 2026
Merged
Conversation
Each SDLC skill now checks for a knowledge graph at .understand-anything/knowledge-graph.json and invokes /understand-chat as a sub-step during context gathering. The graph query logic stays in /understand-chat — no duplication across skills. Skills degrade gracefully when no graph exists.
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
Add a "Gather knowledge graph context" step to each SDLC lifecycle skill (
/issue,/implement,/test,/commit,/pr,/review) that invokes/understand-chatas a sub-step during context gathering. When.understand-anything/knowledge-graph.jsonexists, each skill queries it with task-appropriate keywords before planning or analyzing code. When no graph exists, the step is skipped silently and the skill continues as before.The graph query logic lives exclusively in
/understand-chat— no duplication across skills.Closes #158
Proposed changes
Knowledge graph context step in five skills
Add a new numbered step "Gather knowledge graph context" to
/issue(step 3),/test(step 2),/commit(step 4),/pr(step 4), and/review(step 5). Each step checks for the graph file, invokes/understand-chatwith a skill-derived query, and provides a purpose statement explaining what the context informs. TL;DR lists and subsequent step numbers are renumbered accordingly.The query source varies per skill:
/issue— conversation context (the user's description)/test— changed file paths/commit— changed file paths from the diff/pr— changed files and branch diff summary/review— changed file paths from the PR diffKnowledge graph context bullet in
/implementAdd a bullet to the existing "Gather context" step (step 6) rather than a new numbered step, since
/implementalready has a dedicated context-gathering phase. The bullet invokes/understand-chatwith the issue title and body.