code-review-context

Enforces bounded, cache-stable context construction rules for model inference requests.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/sjc786526-coder/RONDO --skill code-review-context-sjc786526-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-context
Source: https://github.com/sjc786526-coder/RONDO/tree/main/multidev/.codex/skills/code-review-context
Command: npx skills add https://github.com/sjc786526-coder/RONDO --skill code-review-context-sjc786526-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When building an agent harness, uncontrolled growth of the model context causes cache misses, unbounded token usage, and unpredictable inference behavior. This Skill gives reviewers a concrete checklist to audit how conversation context is assembled before it is sent to the model. ## Core Features & Use Cases - Incremental History Rule: Verifies that context is built up incrementally with no history rewrites, preserving prompt cache hits. - Bounded Item Enforcement: Checks that every injected item has a hard size cap, with no item exceeding 10K tokens. - P0 Escalation: Flags any new individual item that can cross 1K tokens for mandatory manual review. - Structural Requirement: Ensures all injected fragments are defined as structs in core/context implementing the ContextualUserFragment trait. - Use Case: During code review of a change that injects a new system reminder or tool output into the prompt, apply this Skill to confirm the fragment is bounded, typed, and cache-friendly before approving. ## Quick Start Review this pull request against the code-review-context rules and flag any context items that are unbounded or exceed the token caps.

Frequently Asked Questions about code-review-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review changes to LLM prompt context construction?▼

Check that context is built incrementally without history rewrites, every injected item has a bounded size with a hard cap, and no single item exceeds 10K tokens. New items that can cross 1K tokens require a P0 manual review.

What rules prevent LLM prompt cache misses in an agent harness?▼

Avoid frequent changes to context and never rewrite history, since both invalidate cached prefixes. Context must be built up incrementally so previously sent prefixes remain stable across inference requests.

Is there a token limit for items injected into model context?▼

Yes, every injected item must have a bounded size with a hard cap, and no item may exceed 10K tokens. Items that can individually cross 1K tokens are highlighted as P0 and need additional manual review.

How should new context fragments be implemented in the codebase?▼

All injected fragments must be defined as structs in the core/context module and implement the ContextualUserFragment trait. This ensures every fragment is typed, reviewable, and subject to the bounding rules.

When does a context change need manual review?▼

A change needs manual review when it introduces a new individual context item that can cross 1K tokens, which is flagged as P0. Unbounded items or items over 10K tokens are not allowed at all.