context-scope

Estrellas5

Forks0

Actualizado26 de marzo de 2026 a las 17:17

Surface @context annotations before editing a file. Shows critical constraints, tradeoffs, and risks sorted by priority. Use when about to modify unfamiliar or complex code, or when the user asks what constraints apply to a file.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

recallnet

recallnet/codecontext

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	context-scope
description	Surface @context annotations before editing a file. Shows critical constraints, tradeoffs, and risks sorted by priority. Use when about to modify unfamiliar or complex code, or when the user asks what constraints apply to a file.
user-invocable	true
allowed-tools	Bash(npx codecontext *)
argument-hint	<file>

Run the codecontext scope command on the target file to surface all @context annotations sorted by priority.

npx codecontext --scope $ARGUMENTS

Present the results grouped by priority:

Critical — MUST read before editing. Violating these risks defects or constraint violations.
High — SHOULD read. Significantly reduces risk of unintended consequences.
Normal/Low — Informational context.

If any annotations contain {@link file:.claude/skills/.../SKILL.md} references, tell the user which skill to load before editing that code.

If annotations have review-required or stale status, flag them and recommend the user verify or update the [verified:YYYY-MM-DD] date.

Más de este repositorio

mismo repositorio

codecontext-setup

recallnet/codecontext

Set up or repair codecontext adoption in a project. Use this whenever the user wants to add @context annotations to a repo, install the codecontext toolchain, update AGENTS.md guidance, improve agent workflows around decision capture, or audit whether an existing codecontext setup is coherent. Prefer this skill over vague "document the tool" work: it is specifically for making a repo actually usable with codecontext.

2026-04-225

context-diff

recallnet/codecontext

Check which @context annotations are affected by recent code changes. Use after editing code to verify context accuracy and flag stale annotations.

2026-03-265

context-staged

recallnet/codecontext

Check all staged files for stale @context annotations before committing. Use as a pre-commit verification step.

2026-03-265

name	context-scope
description	Surface @context annotations before editing a file. Shows critical constraints, tradeoffs, and risks sorted by priority. Use when about to modify unfamiliar or complex code, or when the user asks what constraints apply to a file.
user-invocable	true
allowed-tools	Bash(npx codecontext *)
argument-hint	<file>

Run the codecontext scope command on the target file to surface all @context annotations sorted by priority.

npx codecontext --scope $ARGUMENTS

Present the results grouped by priority:

Critical — MUST read before editing. Violating these risks defects or constraint violations.
High — SHOULD read. Significantly reduces risk of unintended consequences.
Normal/Low — Informational context.

If any annotations contain {@link file:.claude/skills/.../SKILL.md} references, tell the user which skill to load before editing that code.

If annotations have review-required or stale status, flag them and recommend the user verify or update the [verified:YYYY-MM-DD] date.