Skip to content

Revert "fix(uipath-planner): trim genome-format-guide under Codex's 40,000-byte read (optimizer, gated)" - #4906

Merged
RaduAna-Maria merged 1 commit into
mainfrom
revert-4810-fix/uipath-planner-genome-format-codex-read
Nov 18, 2026
Merged

RaduAna-Maria merged 1 commit into
mainfrom
revert-4810-fix/uipath-planner-genome-format-codex-read

Conversation

@RaduAna-Maria

Copy link
Copy Markdown
Collaborator

Reverts #4810

@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @RaduAna-Maria's task in 39s —— View job


Summary

Straight git revert of #4810. It puts skills/uipath-planner/references/shared/genome-format-guide.md back to its pre-trim text: 34,937 → 43,256 bytes, +93/−101.

Change-by-Change Review

1. Is the revert clean?

OK

2. The AGENT-READ-TRUNCATED warning comes back

Medium

  • At 43,256 bytes, the file is over the 40,000 bytes Codex keeps from one read. skill-lint already flags this on this PR.
  • Codex drops the middle of an over-cap read, so Codex agents will again miss part of this guide when they read it whole.
  • fix(uipath-planner): trim genome-format-guide under Codex's 40,000-byte read (optimizer, gated) #4810's re-gate on codex / gpt-5.6-luna showed the trim helping: 9/14 → 11/14, with genome-from-solution-sdd-case-child going 0/2 → 2/2. Reverting should bring that regression back on Codex.
  • Fix: add the reason for the revert to the PR body: a dropped rule, a failing eval, or a wording problem. If one specific cut caused the problem, restoring only that passage keeps the file under 40 KB and fixes the issue. If the full revert is intentional, follow up with a new trim or a split, for example moving Handoffs and the Source Map into a separate reference.

What's Missing

Area Ratings

Area Status Notes
Frontmatter OK Not touched
E2E Tests OK No new capability; existing planner genome tasks cover the file
Skill Body OK Not touched
References & Assets Issue Over the Codex 40 KB single-read cap again
Repo Hygiene OK Change stays in one skill; no secrets or personal paths

Issues for Manual Review

Conclusion

The revert itself is mechanically correct. It does knowingly reintroduce the Codex truncation that #4810 fixed, and the PR doesn't say why. Request changes: at minimum, add the rationale. Better: revert only the passage that caused the problem.

@github-actions

Copy link
Copy Markdown
Contributor

skill-lint: 0 new errors, 1 new warning

Rule Location Message
warning AGENT-READ-TRUNCATED skills/uipath-planner/references/shared/genome-format-guide.md:1 43,256 bytes, 238 lines: Codex keeps 10,000 tokens (40,000 bytes) of one read. Split it or route to smaller files
What these rules check
  • AGENT-READ-TRUNCATED: Markdown files an agent reads should fit in one read of each target agent. Each agent caps what one read returns. Codex keeps 10,000 tokens, counted as UTF-8 bytes / 4, and drops the middle. Delegate's ReadFile, which LoadSkill also uses, returns the first 2,000 lines and at most 100,000 characters of them. Claude Code's Read returns the first ~25,000 tokens with a partial-view notice and, by default, refuses a whole file over 256 KB. Gemini CLI's read_file returns the first 2,000 lines and cuts lines over 2,000 characters. Past a cap the agent sees part of the file unless it reads it in pages. Split the file, or move detail into smaller references the skill routes to. SKILL.md is checked for Codex and Delegate only: Claude Code and Gemini load it whole when the skill activates. Claude Code's count is real tokens, estimated with claude_code_bytes_per_token; the others are exact.

Only what this PR adds is listed, compared with the commit it branched from; issues already on the base branch are not. Updated on every push.

@RaduAna-Maria
RaduAna-Maria merged commit 329e3d4 into main Nov 18, 2026
47 of 48 checks passed
@RaduAna-Maria
RaduAna-Maria deleted the revert-4810-fix/uipath-planner-genome-format-codex-read branch November 18, 2026 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant