Detect drift between stale engineering proposals and current codebases.
npx skills add https://github.com/Sharper-Flow/Advance --skill adv-refactor
Please help me install this Agent Skill. Skill: adv-refactor Source: https://github.com/Sharper-Flow/Advance/tree/main/skills/adv-refactor Command: npx skills add https://github.com/Sharper-Flow/Advance --skill adv-refactor
This skill resolves the disconnect between outdated engineering proposals and the current state of the codebase, preventing scope drift and ensuring that documentation remains a reliable source of truth.
Run the adv-refactor skill to refresh the stalest active proposals and align them with the current implementation.
High-intent search queries and answers about installing and using this skill.
To reconcile stale engineering proposals with current code, you need to perform drift scanning and obsolescence detection against historical archives. This process aligns outdated proposal requirements with actual implementation evidence using hash matching and fuzzy similarity.
The best way to detect proposal drift is to scan active change sets by comparing proposal requirements against the actual implementation evidence. Hash matching and fuzzy similarity identify overlaps with archived changes and flag obsolete requirements.
To batch refactor multiple stale proposals safely, process active change sets by prioritizing the oldest items first. This maintains project momentum while dependency verification and conflict resolution identify overlaps with archived changes to keep efforts focused.
Yes, dependency verification prevents scope drift during a proposal refresh by validating structured state mutations. It ensures that proposal requirements align with actual implementation evidence before changes are applied to the codebase.
You should avoid automated proposal reconciliation when structured state mutation and validation logic cannot be applied to your active change sets. Without historical archives and dependency verification, automated staleness analysis may incorrectly flag or overwrite valid implementation evidence.
Yes, proposal refresh requires structured state mutation and validation logic to function correctly. This logic ensures that detected obsolescence and drift scanning results accurately align proposal requirements with the actual implementation evidence.
riandeoliveiraScan Git repositories with Gitleaks to detect and prevent hardcoded credentials.
cryborg1211Analyze codebases to generate and maintain structured project documentation.
open-platform-modelDetect conflicting OpenSpec changes and generate a structured harmony report.
TrevorMannAutomate record linkage with configurable match rules and fuzzy matching.
