Maintain repository context memory documenting architecture, subsystem interfaces, and risks.
npx skills add https://github.com/Capataina/agent-skills --skill upkeep-context
Please help me install this Agent Skill. Skill: upkeep-context Source: https://github.com/Capataina/agent-skills/tree/main/upkeep-context Command: npx skills add https://github.com/Capataina/agent-skills --skill upkeep-context
Maintains a repository-level context folder as durable implementation memory — a living memory of current implementation reality, subsystem boundaries, decisions, and lessons that helps future engineers understand and safely change the project without re-deriving everything from code.
Invoke the upkeep-context workflow to initialise or refresh the repository memory by scanning the repository and producing canonical context documents grounded in current code reality.
High-intent search queries and answers about installing and using this skill.
You can preserve repository memory by maintaining a context/ folder that documents architecture anchors, subsystem boundaries, and decision rationale to ground future engineering work in current code reality.
Linting repository context involves deterministic upkeep activities like scanning the repository to ensure the memory layer accurately reflects current interfaces, trade-offs, and canonical ownership boundaries.
A context folder provides durable implementation memory that documents cross-system alignment and risks, enabling engineers to safely repair or restructure subsystems without re-deriving boundaries from code.
Yes, repository memory stores canonical references, durable notes, and guiding principles that document subsystem interfaces, allowing new engineers to understand implementation reality on-demand.
A context folder is essential when repositories have complex subsystem boundaries and cross-system alignment needs, serving as a living memory that tracks decisions, risks, and trade-offs across sessions.
Repository context drifts because code changes outpace documentation, requiring deterministic repo scanning and context linting to realign durable notes and references with current code boundaries.
kennypallchizaca-coderDefine persistence layers with entities, repository interfaces, and migrations.
WesleyMFrederickLoad architecture principles and core conventions from documentation files for project alignment.
VoDaiLoczAutomate linting and static analysis of code in CI pipelines.
shirulotStandardize Architecture Decision Records and technical documentation with templates for ADRs, READMEs, and inline code annotations.
