workspace-maintenance

Maintain Codex Workspace consistency across docs, scripts, caches, and repo conventions.

2|Updated Mar 17, 2026

Search Tags:#automation #maintenance #workspace #governance #docs #scripts #repositories

Ready to run

npx skills add https://github.com/RichardGeorgeDavis/Codex-Workspace --skill workspace-maintenance-richardgeorgedavis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workspace-maintenance
Source: https://github.com/RichardGeorgeDavis/Codex-Workspace/tree/main/shared/skills/workspace-maintenance
Command: npx skills add https://github.com/RichardGeorgeDavis/Codex-Workspace --skill workspace-maintenance-richardgeorgedavis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains the Codex Workspace's stability by preventing drift across docs, scripts, caches, and repo conventions, keeping the environment predictable for agents and users.

Core Features & Use Cases

Governance of workspace-level conventions to avoid duplication and misalignment across repos
Guidance via a default workflow and recommended scripts to maintain consistency
Onboarding and maintenance scenarios: adding new repos, refreshing caches, and adjusting tooling while preserving locality

Quick Start

Run the default workspace maintenance workflow to verify alignment and apply recommended local adjustments.

Frequently Asked Questions about workspace-maintenance

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

FAQPage Schema

How do I maintain workspace consistency across multiple local repositories?▼

Workspace consistency across local repositories is maintained by applying a documented governance workflow that enforces shared conventions for docs, scripts, and caches. This prevents drift and cross-repo dependency contamination during setup and upgrades.

What is workspace drift and how does it affect local development environments?▼

Workspace drift happens when documentation, scripts, caches, and repo conventions become misaligned across local repositories. It creates unpredictable environments, requiring governance workflows and automation to realign shared resources and maintain stability.

How do I prevent cross-repo dependency contamination when coordinating local repositories?▼

Prevent cross-repo dependency contamination by enforcing a documented workflow with guardrails and utilizing optional resource directories like scripts/, references/, and assets/. This structure guides automation while preserving strict repository locality and preventing shared tooling conflicts.

What's the best way to govern workspace-level conventions for shared caches and tooling?▼

Governing workspace-level conventions is best achieved by running a default maintenance workflow that verifies alignment and applies local adjustments. This governs shared caches and tooling to avoid duplication and misalignment across repos.

Does workspace governance work when adding new repositories or refreshing caches?▼

Workspace governance works for adding new repositories and refreshing caches by applying a documented workflow with guardrails. This ensures onboarding and maintenance scenarios preserve locality, keep environments aligned, and prevent drift.

When should I use a workspace maintenance workflow for repo-level conventions?▼

Use a workspace maintenance workflow when coordinating many local repos, handling shared caches, or adjusting tooling during upgrades. It enforces repo-level conventions to keep the environment predictable for agents and users.