Track code change intent and drift through a SQLite property graph.
npx skills add https://github.com/lciacci/tessera --skill icpg-lciacci
Please help me install this Agent Skill. Skill: icpg Source: https://github.com/lciacci/tessera/tree/main/skills/icpg Command: npx skills add https://github.com/lciacci/tessera --skill icpg-lciacci
iCPG prevents developers and autonomous agents from changing code without understanding its original purpose, constraints, ownership, and risk. It reduces duplicated effort and exposes when implementation drifts from the intent and contracts that created it.
Initialize the iCPG graph, create an intent for your planned change, run the three pre-task queries, record modified symbols, and check for drift before fulfilling the intent.
High-intent search queries and answers about installing and using this skill.
Architectural drift detection compares recorded code symbols and contract predicates against the current codebase to identify when implementation has deviated from the original intent and constraints. It exposes invalidated purpose and ownership risk before changes are merged.
You can track code intent by creating ReasonNodes in an intent-augmented code property graph. Query prior work, inspect file constraints and symbol risk profiles, then record modified symbols to check whether existing contracts still hold.
Yes, you can bootstrap intents from Git history to populate the intent graph. This optional workflow records prior work and constraints into a per-project SQLite graph, establishing a baseline for future drift analysis and contract validation.
A code property graph prevents duplicate work by connecting goals, decisions, owners, and contracts to specific code symbols. Before starting a task, developers query prior work to understand existing constraints and avoid overlapping efforts.
You need a per-project SQLite graph to run drift analysis. This local database stores the intent-augmented code property graph, including symbol checksums, contract predicates, and ReasonNodes required for pre-task queries and drift detection.
You should run contract validation before and after code changes. Pre-task queries inspect constraints and risk profiles, while post-change drift detection checks whether recorded contract predicates still hold against the modified symbols.
GoldziherIndex and query large codebases for structural insight without reading files.
alinaqiTrack code changes against formal contracts using a Reason Graph.
jasonkneenOutsource coding tasks to the Claude Code CLI for automated development.
driftinglyAnalyze React source code for security, performance, correctness, and architecture issues.
