chameleon-refresh

Re-analyze repositories to update chameleon profiles and detect code drift.

9|3|Updated May 10, 2026

Search Tags:#code analysis #repository management #repository analysis #profile update #code drift detection

Ready to run

npx skills add https://github.com/crisnahine/chameleon --skill chameleon-refresh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chameleon-refresh
Source: https://github.com/crisnahine/chameleon/tree/main/plugin/skills/chameleon-refresh
Command: npx skills add https://github.com/crisnahine/chameleon --skill chameleon-refresh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that the chameleon profile is up-to-date with the current state of the repository, providing accurate code analysis and suggestions.

Core Features & Use Cases

Re-analysis: Automatically re-analyze the repository to detect code drift and update the chameleon profile.
Partial Refresh: Perform a partial refresh when less than 10% of files have changed, using cached data for efficiency.
Full Re-bootstrap: Perform a full re-bootstrap when more than 10% of files have changed, ensuring the profile is fully up-to-date.
Production Pinned Repos: Handle production-pinned repositories by fetching the latest production code before refreshing the profile.
Unpinned Repos: Re-discover files and re-parse changed files for unpinned repositories.
Incremental Refresh: Use partial refresh for incremental updates to save time.
Offer Auto-idiom: Suggest running the /chameleon-auto-idiom skill when no idioms are present in the profile.

Quick Start

Run the /chameleon-refresh command to re-analyze the current repository and update the chameleon profile.

Frequently Asked Questions about chameleon-refresh

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I update my code analysis profile after repository changes?▼

To update a code analysis profile after repository changes, re-analyze the repository to detect code drift and refresh the profile based on the file change ratio. The system performs a partial refresh using cached data or a full re-bootstrap depending on the changes.

When should I perform a partial refresh versus a full re-bootstrap?▼

Perform a partial refresh when less than 10% of files have changed to use cached data efficiently, and trigger a full re-bootstrap when more than 10% of files have changed to ensure the profile is fully up-to-date.

Does repository refresh work with production-pinned repositories?▼

Repository refresh handles production-pinned repositories by fetching the latest production code before refreshing the profile, while unpinned repositories undergo file re-discovery and re-parsing of changed files.

What are the limitations of incremental refresh for code drift detection?▼

Incremental refresh for code drift detection is limited to scenarios with less than 10% file changes for cached efficiency. Larger changes require a full re-bootstrap, and the tool only suggests running an auto-idiom skill rather than generating idioms directly.