← Codex Dev WorkflowsCONTENT HISTORY

Update to Codex Dev Workflows

Snapshot Sep 30, 2026 · 23:15 UTC · version 0.4.2

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Implement a focused software feature with scoped investigation, verification, and a clear completion report.",
  "included_files": [],
  "name": "feature-development",
  "skill_md_contents": "---\nname: feature-development\ndescription: Implement a focused software feature with scoped investigation, verification, and a clear completion report.\n---\n\n# Feature development workflow\n\nUse this skill to implement a requested feature or small enhancement. First read the repository's agent instructions and only the documentation relevant to the task. If the project uses Flutter, JavaScript/TypeScript, Python, or Laravel/PHP, load the corresponding file in `../../shared/platforms/`.\n\n## Understand and scope\n\n1. State the intended behavior, acceptance criteria, constraints, and non-goals.\n2. Trace the smallest relevant code path and identify affected interfaces, state, data, and tests.\n3. Ask for clarification only if ambiguity would change user-visible behavior, data handling, or scope.\n4. Keep existing behavior stable unless the request explicitly changes it.\n\n## Implement\n\n- Make the smallest coherent change that satisfies the acceptance criteria.\n- Match established project conventions and abstractions.\n- Keep error, empty, loading, authorization, and lifecycle behavior deliberate where applicable.\n- Update documentation only when it is part of the interface, behavior, or maintenance contract.\n- Do not perform unrelated refactors, dependency upgrades, or formatting churn.\n\n## Verify\n\nRun the checks relevant to the edited code using repository-defined commands. Add or update meaningful tests for new behavior and boundary cases. Inspect failures rather than hiding them. If a check cannot run, state why and provide the safest next step.\n\n## Final response\n\nReport the behavior delivered, files/components changed, validation performed and result, tests added/updated, and any remaining manual verification or follow-up. Do not claim full verification beyond the evidence available.\n\n"
}

SHA-256 of public snapshot: da9b9a47a5e78ab4f9839bc8344ea6100b1039c961f4704f53c52bf33ce7ff9e