context-diff

Estrelas5

Forks0

Atualizado26 de março de 2026 às 17:17

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

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

recallnet

recallnet/codecontext

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	context-diff
description	Check which @context annotations are affected by recent code changes. Use after editing code to verify context accuracy and flag stale annotations.
user-invocable	true
allowed-tools	Bash(npx codecontext *)
argument-hint	<file>

Run the codecontext diff command on the target file to see which annotations are affected by uncommitted changes.

npx codecontext --diff HEAD $ARGUMENTS

For each affected annotation:

Check if the annotation still accurately describes the code.
If accurate, recommend bumping [verified:YYYY-MM-DD] to today's date.
If no longer accurate, recommend updating the annotation summary.
If the annotated code was removed, recommend removing the annotation.

Flag any !critical annotations that changed — these require careful review.

Mais deste repositório

mesmo repositório

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-scope

recallnet/codecontext

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.

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-diff
description	Check which @context annotations are affected by recent code changes. Use after editing code to verify context accuracy and flag stale annotations.
user-invocable	true
allowed-tools	Bash(npx codecontext *)
argument-hint	<file>

Run the codecontext diff command on the target file to see which annotations are affected by uncommitted changes.

npx codecontext --diff HEAD $ARGUMENTS

For each affected annotation:

Check if the annotation still accurately describes the code.
If accurate, recommend bumping [verified:YYYY-MM-DD] to today's date.
If no longer accurate, recommend updating the annotation summary.
If the annotated code was removed, recommend removing the annotation.

Flag any !critical annotations that changed — these require careful review.