opencode-gitlab-dap 1.8.4 → 1.9.0

package/dist/index.cjs

@@ -2259,7 +2259,30 @@ This project may have persistent memory and skills available via knowledge tools
 Use gitlab_memory_load to check for existing project context (facts, decisions, patterns).
 Use gitlab_skill_list to discover available task-specific skills.
 When you learn something new about the project, use gitlab_memory_record to preserve it.
-When you complete a significant task, consider using gitlab_memory_log_session to log learnings.`;
+When you complete a significant task, consider using gitlab_memory_log_session to log learnings.
+
+### Bootstrap Project Memory
+When the user says "bootstrap project memory", "initialize memory", or "build project knowledge":
+1. FIRST: Determine the project path by running \`run_git_command("remote", ["-v"])\` and extracting the path from the git remote URL (e.g., "git@gitlab.com:my-group/my-project.git" \u2192 "my-group/my-project"). NEVER guess the project path.
+2. Call gitlab_memory_load with the extracted project path to check if memory already exists.
+3. If memory exists, show a summary and ask if the user wants to refresh it.
+4. If memory is empty (or user wants refresh), gather project knowledge by:
+   a. Read the project README, key config files, and codebase structure (use file/repo tools).
+   b. Fetch project details via gitlab_get_project.
+   c. List open issues (gitlab_list_issues, state=opened, limit=20).
+   d. List open merge requests (gitlab_list_merge_requests, state=opened, limit=10).
+   e. Check recent pipelines (gitlab_list_pipelines, limit=5).
+   f. List project members (gitlab_list_project_members).
+5. Record each category as separate memory entries using gitlab_memory_record:
+   - fact: project overview (name, purpose, tech stack, language, dependencies)
+   - fact: architecture and codebase structure (key files, modules, patterns)
+   - fact: CI/CD pipeline configuration (stages, jobs, deployment targets)
+   - fact: open issues summary (count, key issues, labels)
+   - fact: open MRs summary (count, key MRs, review status)
+   - fact: team and contributors
+   - pattern: development workflow observations (branching, review process, release cycle)
+6. Log a session with gitlab_memory_log_session summarizing the bootstrap.
+IMPORTANT: Always extract the project path from git remote \u2014 never guess it. Fire multiple gitlab_memory_record calls in parallel \u2014 each creates its own page, so parallel writes are safe.`;
 
 // src/hooks.ts
 function buildFlowSubagentPrompt(flow, projectPath, projectUrl) {