c-05-create-or-update-onboarding-files

Create and update file-level onboarding and repo-level entity catalogs with traceable update history.

27|4|Updated Mar 21, 2026

Search Tags:#automation #documentation #onboarding #routing #memory #governance

Ready to run

npx skills add https://github.com/Foxfire1st/agents-remember --skill c-05-create-or-update-onboarding-files

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: c-05-create-or-update-onboarding-files
Source: https://github.com/Foxfire1st/agents-remember/tree/main/.cursor/skills/c-05-create-or-update-onboarding-files
Command: npx skills add https://github.com/Foxfire1st/agents-remember --skill c-05-create-or-update-onboarding-files

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and maintenance of file-level onboarding and repo-level entity catalogs to enforce a strict 1-to-1 source mapping and ensure governance and traceability across the codebase.

Core Features & Use Cases

Coordinated onboarding maintenance for file-level onboarding and repo-level catalogs, ensuring parity and traceability with the repository state.
Route-level change handling: when a change crosses multiple targets (e.g., new packages, renames, moves), coordinate with the c-03-repo-bootstrap skill to apply the correct bootstrap and avoid orphaned onboarding.
Documentation-driven: relies on the Domain Documentation originating from the resolved system/sources.md to anchor evidence, references, and cross-workflow consistency.
Audit-friendly: preserves an append-only Update History, preserves contributing notes, and updates governance-overview links as the repository evolves.

Quick Start

Create or update onboarding for a target repository's concrete source file and its repo-level catalog in a single operation.

Frequently Asked Questions about c-05-create-or-update-onboarding-files

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

FAQPage Schema

How do I automate onboarding file creation and maintain repo catalogs?▼

Automating onboarding file creation enforces strict 1-to-1 source mapping and maintains repo-level entity catalogs. It ensures governance and traceability across your codebase by routing changes and applying deterministic evidence fingerprints.

What is file-level onboarding governance and how does it work?▼

File-level onboarding governance ensures traceability across codebases via strict 1-to-1 source mapping. It anchors evidence using Domain Documentation, preserves append-only Update History, and updates governance-overview links as repositories evolve.

How do I handle route-level changes and package migrations in onboarding files?▼

Handling route-level changes and package migrations requires routing cross-target modifications to coordinated maintenance skills. This prevents orphaned onboarding entries by applying correct bootstrap procedures during multi-target repository transitions.

How do I ensure traceability for repository onboarding updates?▼

Ensuring traceability for repository onboarding updates involves preserving append-only Update History and generating deterministic evidence fingerprints. These mechanisms anchor documentation references and maintain audit-friendly records for codebase governance.

Does onboarding file maintenance work with existing Domain Documentation?▼

Onboarding file maintenance relies directly on Domain Documentation originating from resolved system sources. It anchors evidence, references, and cross-workflow consistency using these existing documentation artifacts.

When should I not use automated onboarding catalog updates?▼

Automated onboarding catalog updates should be avoided when strict 1-to-1 source mapping cannot be enforced or when Domain Documentation is absent, as traceability and governance guarantees depend on these foundational anchors.