Code Refactoring Context Restore

Context Restoration: Advanced Semantic Memory Rehydration

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/code-refactoring-context-restore from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses metadata.json plus ORIGIN.md as the provenance anchor for review.

Context Restoration: Advanced Semantic Memory Rehydration

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Role Statement, Context Overview, Core Requirements and Arguments, Advanced Context Retrieval Strategies, Integration Patterns, Future Roadmap.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Working on context restoration: advanced semantic memory rehydration tasks or workflows
• Needing guidance, best practices, or checklists for context restoration: advanced semantic memory rehydration
• The task is unrelated to context restoration: advanced semantic memory rehydration
• You need a different domain or tool outside this scope
• Use when the request clearly matches the imported source intent: working with code refactoring context restore.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Clarify goals, constraints, and required inputs.
2. Apply relevant best practices and validate outcomes.
3. Provide actionable steps and verification.
4. If detailed examples are required, open resources/implementation-playbook.md.
5. Retrieve most recent project context
6. Validate context against current codebase
7. Selectively restore relevant components

Imported Workflow Notes

Imported: Instructions

• Clarify goals, constraints, and required inputs.
• Apply relevant best practices and validate outcomes.
• Provide actionable steps and verification.
• If detailed examples are required, open resources/implementation-playbook.md.

Imported: Reference Workflows

Workflow 1: Project Resumption

1. Retrieve most recent project context
2. Validate context against current codebase
3. Selectively restore relevant components
4. Generate resumption summary

Workflow 2: Cross-Project Knowledge Transfer

1. Extract semantic vectors from source project
2. Map and transfer relevant knowledge
3. Adapt context to target project's domain
4. Validate knowledge transferability

Imported: Role Statement

Expert Context Restoration Specialist focused on intelligent, semantic-aware context retrieval and reconstruction across complex multi-agent AI workflows. Specializes in preserving and reconstructing project knowledge with high fidelity and minimal information loss.

Examples

Example 1: Ask for the upstream workflow directly

Use @code-refactoring-context-restore to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @code-refactoring-context-restore against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @code-refactoring-context-restore for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @code-refactoring-context-restore using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Imported Usage Notes

Imported: Usage Examples

# Full context restoration
context-restore project:ai-assistant --mode full

# Incremental context update
context-restore project:web-platform --mode incremental

# Semantic context query
context-restore project:ml-pipeline --query "model training strategy"

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/code-refactoring-context-restore, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @burp-suite-testing - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @burpsuite-project-parser - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @business-analyst - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @busybox-on-windows - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Imported Reference Notes

Imported: Context Overview

The Context Restoration tool is a sophisticated memory management system designed to:

• Recover and reconstruct project context across distributed AI workflows
• Enable seamless continuity in complex, long-running projects
• Provide intelligent, semantically-aware context rehydration
• Maintain historical knowledge integrity and decision traceability

Imported: Core Requirements and Arguments

Input Parameters

• context_source: Primary context storage location (vector database, file system)
• project_identifier: Unique project namespace
• restoration_mode:
  • full: Complete context restoration
  • incremental: Partial context update
  • diff: Compare and merge context versions
• token_budget: Maximum context tokens to restore (default: 8192)
• relevance_threshold: Semantic similarity cutoff for context components (default: 0.75)

Imported: Advanced Context Retrieval Strategies

1. Semantic Vector Search

• Utilize multi-dimensional embedding models for context retrieval
• Employ cosine similarity and vector clustering techniques
• Support multi-modal embedding (text, code, architectural diagrams)

def semantic_context_retrieve(project_id, query_vector, top_k=5):
    """Semantically retrieve most relevant context vectors"""
    vector_db = VectorDatabase(project_id)
    matching_contexts = vector_db.search(
        query_vector,
        similarity_threshold=0.75,
        max_results=top_k
    )
    return rank_and_filter_contexts(matching_contexts)

2. Relevance Filtering and Ranking

• Implement multi-stage relevance scoring
• Consider temporal decay, semantic similarity, and historical impact
• Dynamic weighting of context components

def rank_context_components(contexts, current_state):
    """Rank context components based on multiple relevance signals"""
    ranked_contexts = []
    for context in contexts:
        relevance_score = calculate_composite_score(
            semantic_similarity=context.semantic_score,
            temporal_relevance=context.age_factor,
            historical_impact=context.decision_weight
        )
        ranked_contexts.append((context, relevance_score))

    return sorted(ranked_contexts, key=lambda x: x[1], reverse=True)

3. Context Rehydration Patterns

• Implement incremental context loading
• Support partial and full context reconstruction
• Manage token budgets dynamically

def rehydrate_context(project_context, token_budget=8192):
    """Intelligent context rehydration with token budget management"""
    context_components = [
        'project_overview',
        'architectural_decisions',
        'technology_stack',
        'recent_agent_work',
        'known_issues'
    ]

    prioritized_components = prioritize_components(context_components)
    restored_context = {}

    current_tokens = 0
    for component in prioritized_components:
        component_tokens = estimate_tokens(component)
        if current_tokens + component_tokens <= token_budget:
            restored_context[component] = load_component(component)
            current_tokens += component_tokens

    return restored_context

4. Session State Reconstruction

• Reconstruct agent workflow state
• Preserve decision trails and reasoning contexts
• Support multi-agent collaboration history

5. Context Merging and Conflict Resolution

• Implement three-way merge strategies
• Detect and resolve semantic conflicts
• Maintain provenance and decision traceability

6. Incremental Context Loading

• Support lazy loading of context components
• Implement context streaming for large projects
• Enable dynamic context expansion

7. Context Validation and Integrity Checks

• Cryptographic context signatures
• Semantic consistency verification
• Version compatibility checks

8. Performance Optimization

• Implement efficient caching mechanisms
• Use probabilistic data structures for context indexing
• Optimize vector search algorithms

Imported: Integration Patterns

• RAG (Retrieval Augmented Generation) pipelines
• Multi-agent workflow coordination
• Continuous learning systems
• Enterprise knowledge management

Imported: Future Roadmap

• Enhanced multi-modal embedding support
• Quantum-inspired vector search algorithms
• Self-healing context reconstruction
• Adaptive learning context strategies

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.