Agent skill · software engineering · neolabhq
actualize
Reconcile the project's FPF state with recent repository changes
Why this skill is useful
Adds a comprehensive executable script for reconciling project state with git changes, ensuring alignment of evidence and decisions with the current codebase.
What it needs
Requires git installed locally. About 2k tokens when loaded. Last updated 2026-08-06. 1,306 stars on the source repository.
What this skill does
Actualize Knowledge Base This command is a core part of maintaining a living assurance case. It keeps your FPF knowledge base (.fpf/) in sync with the evolving reality of your project's codebase. The command performs a three-part audit against recent git changes to surface potential context drift, stale evidence, and outdated decisions. This aligns with the Observe phase of the FPF Canonical Evolution Loop (B.4) and helps manage Epistemic Debt (B.3.4). Action (Run-Time) Step 1: Check Git Changes Run git commands to identify changes since last actualization: Step 2: Analyze Report for Context Drift 1. Review changed files for core project configuration: package.json, go.mod, Cargo.toml, requirements.txt Dockerfile, docker-compose.yml .env.example, config files 2. If configuration files changed: Re-read project structure (README, config files) Compare detected context with .fpf/context.md Present diff to user 3. Ask user if they want to update context.md Step 3: Analyze Report for Evidence Staleness (Epistemic Debt) 1. Read all evidence files in .fpf/evidence/ 2. Check carrierref field in each evidence file 3. Cross-reference with changed files from git diff 4. If a referenced file changed: Flag the evidence as STALE Note which hypothesis is affected Step 4: Analyze Report for Decision Relevance 1. Read all DRR files in .fpf/decisions/ 2. Trace back to source evidence and hypothesis files 3. If foundational files changed: Flag the DRR as POTENTIALLY OUTDATED Step 5: Update Baseline Create/update .fpf/.baseline file: Step 6: Present Findings Output a structured report: File: .fpf/.baseline Track the last actualization point: When to Run Before starting new work: Ensure knowledge base is current After major changes: Sync evidence with code changes Weekly maintenance: Part of regular hygiene Before decisions: Ensure evidence is still valid
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills neolabhq/actualize