Menú
How to ensure new files are included in commits when using the COMMIT command's auto-scoping
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
How the multi-backend adapter system works — AgentAdapter interface, ACP protocol, session resume, and how to add new provider adapters
When debugging why an agent has the wrong provider/model, or when modifying agent creation or delegation flows.
How to get agents to use group chats for peer coordination in flightdeck-based crews. Covers hub-and-spoke anti-pattern, auto-grouping triggers, and file-lock-linked groups. Use when setting up multi-agent crews with 3+ agents or diagnosing why agents aren't collaborating directly.
When fetching from the `/coordination/activity` API and you only need specific action types (e.g., `progress_update`, `task_completed`, `delegated`).
When fetching activity data for UI display, or debugging why activity-based features show empty/stale data.
Architecture decisions and patterns from Flightdeck development (Phases 2–4). Covers feature architecture, state management, component patterns, and API design.
| name | commit-new-files-pattern |
| description | How to ensure new files are included in commits when using the COMMIT command's auto-scoping |
The COMMIT command only stages files that are locked via LOCK_FILE. New files that aren't locked will be left behind as untracked.
ALWAYS use LOCK_FILE on new files before committing.
After committing, run git status to verify nothing was left behind.
This pattern caused issues multiple times (ProjectTabs.tsx, commandParser.ts, AcpOutput.tsx) where committed code referenced new files that weren't included in the commit — breaking the build for other developers.
git status after to verify no untracked files remain that should have been committed