-
Notifications
You must be signed in to change notification settings - Fork 0
refactor(infrastructure): consolidate skills service factories (LISA-58) #212
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.
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
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,56 @@ | ||
| /** | ||
| * Shared git-mem factory with lazy singleton pattern. | ||
| * | ||
| * Provides a single git-mem instance that can be used by both: | ||
| * - Infrastructure DI (bootstrap.ts) | ||
| * - Skills entry points (memory.ts, tasks.ts, etc.) | ||
| * | ||
| * This consolidates the duplicate factory patterns from: | ||
| * - skills/shared/clients/GitMemFactory.ts | ||
| * - bootstrap.ts inline creation | ||
| */ | ||
|
|
||
| import { MemoryService, NotesService, MemoryRepository } from 'git-mem/dist/index'; | ||
| import type { IMemoryService as IGitMemMemoryService } from 'git-mem/dist/index'; | ||
|
|
||
| /** Lazy singleton instance */ | ||
| let gitMemInstance: IGitMemMemoryService | null = null; | ||
|
|
||
| /** | ||
| * Get or create the shared git-mem MemoryService instance. | ||
| * | ||
| * Uses lazy initialization - the instance is created on first call | ||
| * and reused for subsequent calls within the same process. | ||
| * | ||
| * @returns The git-mem MemoryService instance | ||
| */ | ||
| export function getGitMemInstance(): IGitMemMemoryService { | ||
| if (!gitMemInstance) { | ||
| const notes = new NotesService(); | ||
| const repo = new MemoryRepository(notes); | ||
| gitMemInstance = new MemoryService(repo); | ||
| } | ||
| return gitMemInstance; | ||
| } | ||
|
|
||
| /** | ||
| * Create a fresh git-mem MemoryService instance. | ||
| * | ||
| * Use this when you need an isolated instance (e.g., for testing) | ||
| * rather than the shared singleton. | ||
| * | ||
| * @returns A new git-mem MemoryService instance | ||
| */ | ||
| export function createGitMem(): IGitMemMemoryService { | ||
| const notes = new NotesService(); | ||
| const repo = new MemoryRepository(notes); | ||
| return new MemoryService(repo); | ||
| } | ||
|
|
||
| /** | ||
| * Reset the singleton instance (for testing only). | ||
| * @internal | ||
| */ | ||
| export function resetGitMemInstance(): void { | ||
| gitMemInstance = null; | ||
| } |
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
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
45 changes: 16 additions & 29 deletions
45
...b/skills/shared/services/PromptService.ts → ...astructure/services/SkillPromptService.ts
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bootstrapContainernow always takes the process-widegetGitMemInstance()path, which means all later container bootstraps reuse the first git-mem backend created in this process. Since that singleton is not keyed byprojectRoot, any multi-repo usage in one process (e.g., repeated bootstrap calls in adapters/tests or long-lived hosts) can persist/read memory and tasks against the wrong repository state; this is a data-isolation regression compared to constructing a fresh instance per bootstrap.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the detailed analysis! Let me explain why this is safe in Lisa's architecture:
git-mem is stateless regarding
cwd:NotesService.read/write/list()takescwdas a parameter on each method callMemoryRepository.create/query/delete()passescwdthrough to NotesServiceLisa's usage pattern:
For tests:
resetGitMemInstance()which tests can call between bootstrap invocationsFallback behavior:
When
cwdis not passed (as in Lisa's services), git-mem defaults toprocess.cwd()at execution time - which is correct for our CLI/hook pattern since they're always invoked from the project root.If we need multi-repo support in the future, we could add explicit
cwdpassing to the skill services, but for current usage the singleton is safe.