cbm-artifact-export

Force a full artifact export for codebase-memory-mcp when incremental.noop skips it.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/poyhsiao/agent-skills --skill cbm-artifact-export
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cbm-artifact-export
Source: https://github.com/poyhsiao/agent-skills/tree/main/cbm-artifact-export
Command: npx skills add https://github.com/poyhsiao/agent-skills --skill cbm-artifact-export

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the issue of silent no-ops in the index_repository process when the project DB already exists and no source files changed, resulting in no artifact generation. It ensures artifacts are produced for team members to skip reindexing.

Core Features & Use Cases

  • Force Export: Ensures artifacts are generated even when the incremental.noop path is taken.
  • Artifact Verification: Provides verification steps to confirm the artifact is on disk and correctly created.
  • Commit Decision: Informs the user of the implications of committing the artifact to git or ignoring it.

Quick Start

Run the cbm-artifact-export skill to force the export of the team artifact for codebase-memory-mcp.

Frequently Asked Questions about cbm-artifact-export

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does codebase-memory-mcp skip artifact generation when no source files changed?

Codebase-memory-mcp skips artifact generation due to an incremental.noop behavior that triggers when the project DB exists and detects no source file changes. This Skill forces a full artifact export to override this default path.

How do I force a full artifact export for codebase-memory-mcp?

To force a full artifact export, you must delete the existing project DB to bypass the incremental.noop behavior. This Skill then guides you through generating the team artifact and verifying its presence on disk.

How can I verify if the codebase-memory-mcp team artifact was successfully exported to disk?

This Skill provides built-in artifact verification steps to confirm the exported team artifact is correctly created and exists on disk after forcing the full export process for codebase-memory-mcp.

Should I commit the exported codebase-memory-mcp team artifact to git?

Committing the team artifact to git allows team members to skip reindexing the codebase. This Skill informs you of the implications of committing the artifact to git or ignoring it.

What are the limitations of forcing a codebase-memory-mcp artifact export?

The main limitation is that forcing a full artifact export requires deleting the project DB. This destructive prerequisite ensures the incremental.noop path is bypassed but resets the existing indexing state.