Skill Claude CodeCodex
Part of agentskel
When reading or writing to Jira tickets or Confluence pages via MCP tools. Use before any Jira transition, ticket creation, or Confluence page update to avoid common failure modes.
The skeleton for agentic development — persistent memory, shared standards, and structured workflows for AI coding agents.
Skill Claude CodeCodex
Part of agentskel
When reading or writing to Jira tickets or Confluence pages via MCP tools. Use before any Jira transition, ticket creation, or Confluence page update to avoid common failure modes.
Skill Claude CodeCodex
Part of agentskel
When reviewing a PR, auditing code quality, or validating changes against the project's standards and sacred behaviors.
Skill Claude CodeCodex
Part of agentskel
When searching for code, tracing a bug, or understanding how modules connect. Use before grepping blindly — consult the index first.
Skill Claude CodeCodex
Part of agentskel
When adding, renaming, or removing a field on a data model that has a mapped counterpart elsewhere — an API/DTO, a database/ORM entity, a serializer, or a cross-platform equivalent model (Android/iOS/Backend). Use whenever a model's fields change, before considering the change complete.
Skill Claude CodeCodex
Part of agentskel
When writing, reviewing, or running a database schema migration — adding, dropping, or altering tables, columns, indexes, or constraints — with any migration tool (Alembic, Rails, Prisma, Room, Core Data, Flyway, Liquibase, raw SQL). Use before generating a migration file, or when one appears in a diff/PR.
Skill Claude CodeCodex
Part of agentskel
When writing, modifying, or reviewing application code. Provides code quality standards, SOLID principles, design philosophy, and platform-specific implementation guidance.
Skill Claude CodeCodex
Part of agentskel
When a design discussion or evaluation is interrupted by a task or workflow, or when the user says "present the discussion," "where were we," "show me the discussion," or "resume" — save or resurface the discussion state using Session Notes.
Skill Claude CodeCodex
Part of agentskel
When working on features that require domain knowledge — business rules, terminology, or invariants specific to this project. [Replace this description and the content below with your project's domain.].
Skill Claude CodeCodex
Part of agentskel
Git branching, commit, and PR procedures. Use when creating branches, making commits, or opening pull requests. Enforces branch naming, commit message format, and PR rules.
Skill Claude CodeCodex
Part of agentskel
When deciding where to store a piece of knowledge (memory files vs Confluence vs Jira). Use when about to document something, capture a lesson, create a ticket, or publish a decision.
Skill Claude CodeCodex
Part of agentskel
Session initialization procedure. Checks memory mount, reads all required memory files, validates skeleton version, checks dependency freshness, and surfaces alerts. Must be executed at the start of every session before any other work.
Skill Claude CodeCodex
Part of agentskel
When creating a new skill or workflow, or improving an existing skill's effectiveness. Use when the user asks to add a capability, write a new workflow, or when a skill isn't triggering or being followed reliably.
Skill Claude CodeCodex
Part of agentskel
When delegating work to a subagent — implementation, review, research, or exploration. Use when a task benefits from a fresh context window, parallel execution, or isolated scope.
Skill Claude CodeCodex
Part of agentskel
When applying debugging techniques during any investigation — root cause tracing, bisect, defense-in-depth. Enforces hypothesis-first analysis and prohibits guess-and-check changes. Use standalone or inside the debug-issue workflow.
Skill Claude CodeCodex
Part of agentskel
Post-task checklist for CHANGELOG, TIMELOG, SYMBOLS/MAP, RESUME, and memory commits. Execute after completing a task that modified files outside .memory/. Do NOT run for pure discussion, memory-only maintenance, or skeleton syncs.
Skill Claude CodeCodex
Part of agentskel
When decomposing a feature or spec into implementable subtasks, estimating scope, or orchestrating multi-step work across subagents.
Skill Claude CodeCodex
Part of agentskel
When implementing logic changes during develop-feature or implement-task. Use the Red-Green-Refactor cycle to write a failing test before any production code.
Skill Claude CodeCodex
Part of agentskel
When designing test strategy, analysing coverage, or writing tests outside the TDD cycle. Also use when working with CI pipelines or validating changes end-to-end.
Skill Claude CodeCodex
Part of agentskel
When running long feature implementations, parallel branch work, or build/test scripts that must not interfere with the user's active working directory. Creates isolated execution environments via git worktrees in sibling directories.
Skill Claude CodeCodex
Part of agentskel
When a single new person joins the team. Use when .memory/TEAM.md already exists and you need to append one member (with roles, optional module assignments, and optional Jira account ID) without touching the rest of the roster.
Skill Claude CodeCodex
Part of agentskel
When adding a new platform (subdir with its own git repo) to an existing workspace dispatcher. Runs setup-skeleton in the subdir and updates the workspace config and dispatcher AGENTS.md.
Skill Claude CodeCodex
Part of agentskel
When the user wants to think through a feature idea, explore edge cases, or produce a technical spec before implementation. Use before develop-feature to prevent mid-implementation surprises.
Skill Claude CodeCodex
Part of agentskel
When codebase structure has changed, MAP.md/SYMBOLS.md are missing or stale, or after major refactors and initial setup. Also run when a new module is added or files are moved between modules.
Skill Claude CodeCodex
Part of agentskel
When dependency versions need auditing, Last Dependency Check in CONFIG.md is overdue (14-day cadence), or before starting security-sensitive work.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: