Skip to content

Make Step 2's KB duplicate search visible with a printed log line #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bguidolim merged 2 commits into from
Aug 28, 2026
Merged

Make Step 2's KB duplicate search visible with a printed log line #25

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
662b891
Initial plan
Copilot Aug 27, 2026
b9f78d2
Add printed KB search log to capture skill Step 2
Copilot Aug 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions skills/continuous-learning/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,6 +116,12 @@ Decide what to do, in this order of preference:

Use `Related:` for memories that share root causes, build on each other, contradict each other, or supersede older decisions. Don't cross-link every vaguely overlapping memory.

Print one line recording this search before continuing, matching the Step 4 checks — hidden reasoning is easy to skip, printed output is reviewable:

```
KB search: "<query>" -> <n> hits, <what they covered> -> <branch taken, and the file edited or created>
```

### Step 3: Research (When Appropriate)

**For general topics** — search available documentation sources first (the user may have MCP servers providing official docs for frameworks or libraries), then fall back to web search:
Expand Down