context-diff

Étoiles5

Forks0

Mis à jour26 mars 2026 à 17:17

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

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

recallnet

recallnet/codecontext

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·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.

Plus depuis ce dépôt

même dépôt

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.