Skip to content
cccskills
FreePublished on GitHub

code-review-context

Review code that manages the conversation history and extra information sent to Codex models. Apply rules for incremental history, size limits, cache stability, manual review of large additions, and required implementation structures.

OriginalShow the original description

Model visible context

See how to install

Good for

  • Review changes to conversation history handling
  • Check size limits on information sent to the model
  • Identify large additions requiring manual review
  • Check implementation types for injected fragments

Files included (1)

  • SKILL.md661 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Codex maintains a context (history of messages) that is sent to the model in inference requests.

  1. No history rewrite - the context must be built up incrementally.
  2. Avoid frequent changes to context that cause cache misses.
  3. No unbounded items - everything injected in the model context must have a bounded size and a hard cap.
  4. No items larger than 10K tokens.
  5. Highlight new individual items that can cross >1k tokens as P0. These need an additional manual review.
  6. All injected fragments must be defined as structs in core/context and implement ContextualUserFragment trait

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

babysit-pr

FreeSummary

Monitor a GitHub pull request for review feedback, automated check failures, and merge readiness. Diagnose failures, fix problems caused by the branch, and retry likely temporary failures while continuing to watch for updates.

  • Monitor automated checks after opening a pull request
  • Address actionable review feedback
  • Distinguish code failures from temporary service problems
openinterpreter/openinterpreter68.6KUpdated Oct 11, 2026

Review external integration points for breaking changes that could disrupt existing use. Examine app-server APIs, command-line parameters, configuration loading, and session resumption from saved records, continuing beyond the first issue to cover possible failure paths.

  • Check app-server API compatibility
  • Review changes to command-line parameters
  • Check compatibility of configuration loading
openinterpreter/openinterpreter68.6KUpdated Oct 11, 2026

code-review

FreeSummary

Run a final pull request review using separate agents for each available review skill. Collect all reported issues into a numbered Markdown list, with a specific file path and line number for every finding.

  • Run a final review of a pull request
  • Combine findings from multiple review skills
  • Locate issues by file path and line number
openinterpreter/openinterpreter68.6KUpdated Oct 11, 2026

Assess whether a code change is small enough to review using line-count guidance. For larger changes, examine the actual differences, dependencies, and calling code to suggest reviewable stages and the smallest coherent first step.

  • Check the size of a change before requesting review
  • Assess the scope of a complex logic change
  • Plan reviewable stages for a large change
openinterpreter/openinterpreter68.6KUpdated Oct 11, 2026

Plan and write tests for changes to agent behavior, favoring integration tests that check components together. Identify key logic changes and user-visible behavior to cover, reuse existing helpers, and keep unit tests in dedicated files.

  • Identify test coverage for changes to agent logic
  • Add integration tests for user-visible behavior
  • Organize unit tests in dedicated files
openinterpreter/openinterpreter68.6KUpdated Oct 11, 2026

codex-pr-body

FreeSummary

Update pull request titles and descriptions to explain why a change matters and what it changes. Preserve existing images and important details, summarize relevant verification, and describe the correct scope for linked, dependent pull requests.

  • Rewrite a pull request description before review
  • Add the motivation discussed during development
  • Remove descriptions of changes that were later undone
openinterpreter/openinterpreter68.6KUpdated Oct 11, 2026

See all skills by openinterpreter

Report a problem with this skill