How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/leszekkantorek/context-skills --skill context-maintainBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Maintain Project Context
Goal
Improve the coherence and organization of existing project knowledge while preserving its meaning, rationale, evidence, and conditions of use.
Steps
- Understand the collection and its uses.
- Understand how the knowledge supports project work and how its sources relate.
- Use existing navigation and project guidance to find related sources across directories within the requested scope.
- Use the questions below to examine their contributions and dependencies.
| Question | Identify | Example |
|---|---|---|
| What needs does this knowledge serve? | Questions, decisions, and work that depend on the collection | Release preparation uses both contribution guidance and a validation procedure. |
| Where does related knowledge appear? | Documents and sections that address the same responsibility or situation | Retry rules appear in a provider guide and an architecture decision. |
| What does each source contribute? | Requirements, explanations, procedures, evidence, and their conditions | A contract defines expected behavior; a test report records observed behavior. |
| Which sources establish the applicable decisions? | Accepted choices, rationale, exceptions, and replacements | A later decision replaces one platform's build procedure. |
| What depends on the current organization? | Incoming links, maps, references, and tools that read or write the content | A task map links directly to a section that may move. |
- Add questions when the table does not explain a source's contribution or relationships.
- Continue when the collection's uses and relationships are clear, with gaps explicit.
- Compare related knowledge and identify problems.
- Identify problems that affect interpretation, maintenance, or use of the knowledge found in Step 1.
- Compare related statements by meaning, scope, rationale, authority, and supporting evidence.
- Check consequential claims against their sources when currency or correctness is in doubt.
- Use the table to distinguish problems from useful differences.
| Pattern | Examine | Interpretation |
|---|---|---|
| Repeated knowledge | Do the statements establish the same rule under the same conditions? | Equivalent statements may duplicate one rule. Similar wording alone does not establish duplication. |
| Different scopes | Do different components, environments, or situations explain the difference? | Different conditions may justify separate rules. |
| Conflicting claims | Do the statements disagree under the same conditions? What establishes the intended result? | Incompatible claims under the same conditions indicate a conflict; its resolution may remain uncertain. |
| Outdated content | Has a decision, dependency, or observed behavior changed? | Evidence of change may establish obsolescence. Age alone does not. |
| Fragmented knowledge | Must readers reconstruct one explanation or procedure from scattered fragments? | Scattered fragments are a problem when readers must reconstruct context needed for one use. |
| Overgrown documents | Do independent subjects obscure the content needed for a particular situation? | Independent subjects are a problem when they obscure relevant knowledge or complicate maintenance. |
| Unnecessary instructions | Does a requirement still serve its stated purpose within its scope? | Repetition or a superseded purpose may indicate redundancy; an accepted obligation requires separate consideration. |
| Difficult access | Do links, section boundaries, or intermediate documents prevent selective reading? | Broken references or unnecessary navigation can prevent readers from reaching sufficient knowledge. |
- Identify other problems when the table does not explain an observed difficulty.
- Distinguish intended behavior from implementation observations. A disagreement does not establish which side needs correction.
- Continue when each identified problem has affected sources, an explained consequence, and supporting evidence or explicit uncertainty.
- Determine changes that preserve useful knowledge.
- Choose changes that address the problems from Step 2 while retaining the contributions identified in Step 1.
- Determine where affected knowledge and its necessary context will remain accessible.
- Use the table to choose changes suited to the content and existing organization.
| Change | Choose when | Preserve |
|---|---|---|
| Keep and clarify | Similar statements have meaningful differences | Scope, conditions, and the reason each variant exists. |
| Consolidate | Several locations repeat equivalent knowledge | One maintained source, its rationale and evidence, with references from relevant locations. |
| Connect | Complementary knowledge belongs in separate sources | Links that explain the relationship and when the other source is needed. |
| Split | Independent subjects require different reading or maintenance | Enough context in each part, with links for shared constraints and dependencies. |
| Correct or replace | Evidence establishes an error or a superseding decision | The applicable knowledge, support for the correction, and useful decision history. |
| Remove | A fragment adds no unique knowledge or is demonstrably obsolete | Any still-useful rationale, evidence, exceptions, and references to its replacement. |
| Leave unresolved | Available evidence cannot settle a conflict or justify a change | Competing claims, their sources, and the decision or evidence still needed. |
- Adapt or combine changes when the listed options do not preserve useful knowledge.
- Continue when changes have clear destinations, identified context to retain, and known effects on dependent references.
- Apply the selected changes and repair affected references.
- Apply the changes selected in Step 3.
- Use the table to update affected content and its dependencies.
| Affected content | Action |
|---|---|
| Shared knowledge | Retain the complete meaning in the selected source and replace redundant copies with useful references. |
| Local qualifications | Keep conditions and exceptions beside the content they qualify, or link them with explicit applicability. |
| Rationale and evidence | Keep supporting sources and limitations attached to the claims they support. |
| Moved or replaced content | Update incoming links, section references, and existing replacement records. |
| Navigation | Repair affected routes. Use context-map when the change requires redesigning how situations lead to sources. |
| Dependent tools | Preserve required formats or update affected readers and writers. |
| Unresolved matters | Preserve conflicting claims, uncertainty, and the evidence or decisions needed for resolution. |
- Preserve other affected relationships when the table does not cover them.
- Continue when selected changes and affected references are updated, with incomplete work explicit.
- Check meaning, coherence, and access after the changes.
- Check that the changes resolve the identified problems while preserving useful knowledge and access.
- Compare the revised collection with the contributions from Step 1, problems from Step 2, and changes selected in Step 3.
- Use representative needs from Step 1 to check whether readers can reach sufficient knowledge without unnecessary reading.
- Use the table to assess the results and identify corrections.
| Check | Expected result | Correction |
|---|---|---|
| Knowledge coverage | Useful statements, rationale, evidence, and exceptions remain available | Restore missing content or references. |
| Meaning and authority | Scope and the distinction between decisions, observations, and proposals remain intact | Correct altered obligations, unsupported certainty, or lost conditions. |
| Coherence | Equivalent rules have a clear maintained source; meaningful variants remain distinguishable | Remove residual duplication or restore differences lost during consolidation. |
| Problem resolution | Each identified problem is resolved or remains explicit with its reason | Address overlooked problems or explain why they remain unresolved. |
| Access | Affected links and routes reach sufficient content for representative needs | Repair destinations, missing context, or unnecessary detours. |
| Dependent tools | Affected readers and writers remain compatible with the revised content | Correct incompatible changes or identify the remaining migration need. |
- Add a check when another consequence could affect interpretation, maintenance, or use.
- Correct problems and repeat affected checks, keeping unresolved gaps and review limits explicit.

