Codex sessions do not mount required gitea-workflow skill #551

Closed
opened 2026-07-08 14:26:36 -05:00 by jcwalker3 · 1 comment
Owner

Codex Gitea-Tools author/reviewer tasks require gitea-workflow, but current Codex sessions do not expose that skill.

Observed:

  • ~/.claude/skills/gitea-workflow/SKILL.md exists.
  • ~/.codex/skills does not contain gitea-workflow.
  • Repo contains skills/llm-project-workflow/SKILL.md and canonical workflow files, but they are not mounted as Codex skills.
  • mcp_list_project_skills exposes operational guides such as gitea-pr-creation, gitea-pr-review, gitea-issue-comments, gitea-resolve-task-capability, and redaction-security-review, but not gitea-workflow, git-pr-workflows, or llm-project-workflow.
  • Controller prompts requiring gitea-workflow therefore block in Codex even when Gitea MCP author/reviewer profiles are healthy.

Impact:

  • PR #545 finalization is blocked in Codex even though the author profile is healthy.
  • Sessions may incorrectly proceed without the required workflow wall.
  • Different LLM runtimes now have different workflow skill names/mounts, creating inconsistent behavior and unsafe fallback pressure.

Expected:

  • Codex sessions for Gitea-Tools can invoke the required workflow skill by exact name, or controller prompts and MCP skill inventory use the same exact canonical name.
  • If the checked-in skills/llm-project-workflow is the portable replacement, it should be mounted and discoverable under a stable canonical name.
  • Missing workflow skill should fail clearly during preflight before any Gitea mutation or git mutation is attempted.

Suggested fix:

  • Install or symlink the workflow skill into ~/.codex/skills/gitea-workflow, or mount the checked-in skills/llm-project-workflow as a Codex skill and update controller prompts accordingly.
  • Update mcp_list_project_skills so the control plane exposes the same canonical workflow name used in prompts.
  • Add a preflight that fails clearly when the required workflow skill is missing.
  • Add tests or proof docs showing Claude/Codex/Gemini sessions resolve the same canonical workflow skill name.

Acceptance criteria:

  • A Codex session can invoke the required workflow skill by the canonical name.
  • mcp_list_project_skills includes the canonical workflow skill/router.
  • Controller prompts no longer reference a skill name unavailable to Codex.
  • Missing-skill sessions stop before git/Gitea mutation and return a clear BLOCKED reason.
  • PR #545 can resume only after either the skill is available or a controller explicitly authorizes the checked-in workflow-doc fallback.
Codex Gitea-Tools author/reviewer tasks require `gitea-workflow`, but current Codex sessions do not expose that skill. Observed: - `~/.claude/skills/gitea-workflow/SKILL.md` exists. - `~/.codex/skills` does not contain `gitea-workflow`. - Repo contains `skills/llm-project-workflow/SKILL.md` and canonical workflow files, but they are not mounted as Codex skills. - `mcp_list_project_skills` exposes operational guides such as `gitea-pr-creation`, `gitea-pr-review`, `gitea-issue-comments`, `gitea-resolve-task-capability`, and `redaction-security-review`, but not `gitea-workflow`, `git-pr-workflows`, or `llm-project-workflow`. - Controller prompts requiring `gitea-workflow` therefore block in Codex even when Gitea MCP author/reviewer profiles are healthy. Impact: - PR #545 finalization is blocked in Codex even though the author profile is healthy. - Sessions may incorrectly proceed without the required workflow wall. - Different LLM runtimes now have different workflow skill names/mounts, creating inconsistent behavior and unsafe fallback pressure. Expected: - Codex sessions for Gitea-Tools can invoke the required workflow skill by exact name, or controller prompts and MCP skill inventory use the same exact canonical name. - If the checked-in `skills/llm-project-workflow` is the portable replacement, it should be mounted and discoverable under a stable canonical name. - Missing workflow skill should fail clearly during preflight before any Gitea mutation or git mutation is attempted. Suggested fix: - Install or symlink the workflow skill into `~/.codex/skills/gitea-workflow`, or mount the checked-in `skills/llm-project-workflow` as a Codex skill and update controller prompts accordingly. - Update `mcp_list_project_skills` so the control plane exposes the same canonical workflow name used in prompts. - Add a preflight that fails clearly when the required workflow skill is missing. - Add tests or proof docs showing Claude/Codex/Gemini sessions resolve the same canonical workflow skill name. Acceptance criteria: - A Codex session can invoke the required workflow skill by the canonical name. - `mcp_list_project_skills` includes the canonical workflow skill/router. - Controller prompts no longer reference a skill name unavailable to Codex. - Missing-skill sessions stop before git/Gitea mutation and return a clear BLOCKED reason. - PR #545 can resume only after either the skill is available or a controller explicitly authorizes the checked-in workflow-doc fallback.
jcwalker3 added the status:in-progress label 2026-07-08 21:42:30 -05:00
Author
Owner

Issue claim heartbeat

<!-- gitea-issue-claim-heartbeat:v1 --> **Issue claim heartbeat** - kind: claim - issue: #551 - branch: feat/issue-551-codex-gitea-workflow - phase: claimed - profile: prgs-author - pr: none - blocker: none - next_action: create worktree and begin implementation
sysadmin removed the status:in-progress label 2026-07-09 08:14:33 -05:00
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#551