context-staged

Sterne5

Forks0

Aktualisiert26. März 2026 um 17:17

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

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

recallnet

recallnet/codecontext

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	context-staged
description	Check all staged files for stale @context annotations before committing. Use as a pre-commit verification step.
user-invocable	true
allowed-tools	Bash(npx codecontext *)
context	fork

Run the codecontext staged check across all files in the git staging area.

npx codecontext --staged

If stale annotations are found:

List each stale annotation with its file, line, and reason.
For each, recommend either:
- Bumping [verified:YYYY-MM-DD] to today if the context is still accurate.
- Updating the annotation summary if the context changed.
- Removing the annotation if the code it described was deleted.
Do not proceed with the commit until all annotations are verified.

If all annotations are fresh, confirm that the staged files are clear to commit.

Mehr aus diesem Repository

gleiches Repository

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

name	context-staged
description	Check all staged files for stale @context annotations before committing. Use as a pre-commit verification step.
user-invocable	true
allowed-tools	Bash(npx codecontext *)
context	fork

Run the codecontext staged check across all files in the git staging area.

npx codecontext --staged

If stale annotations are found:

List each stale annotation with its file, line, and reason.
For each, recommend either:
- Bumping [verified:YYYY-MM-DD] to today if the context is still accurate.
- Updating the annotation summary if the context changed.
- Removing the annotation if the code it described was deleted.
Do not proceed with the commit until all annotations are verified.

If all annotations are fresh, confirm that the staged files are clear to commit.