actualize

Q: How do I install actualize?

Run npx skills add https://github.com/neolabhq/context-engineering-kit --skill actualize in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/actualize/ (personal) or .claude/skills/actualize/ (project).

by neolabhq

Reconcile the project's FPF state with recent repository changes

Installs: 1.2K
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/neolabhq/context-engineering-kit --skill actualize

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads actualize automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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:

# Get current commit hash
git rev-parse HEAD

# Check for changes since last known baseline
# (Read .fpf/.baseline file if it exists, otherwise use initial commit)
git diff --name-only <baseline_commit> HEAD

# List all changed files
git diff --stat <baseline_commit> HEAD

Step 2: Analyze Report for Context Drift

Review changed files for core project configuration:
- package.json, go.mod, Cargo.toml, requirements.txt
- Dockerfile, docker-compose.yml
- .env.example, config files
If configuration files changed:
- Re-read project structure (README, config files)
- Compare detected context with .fpf/context.md
- Present diff to user
Ask user if they want to update context.md

Step 3: Analyze Report for Evidence Staleness (Epistemic Debt)

Read all evidence files in .fpf/evidence/
Check carrier_ref field in each evidence file
Cross-reference with changed files from git diff
If a referenced file changed:
- Flag the evidence as STALE
- Note which hypothesis is affected

Step 4: Analyze Report for Decision Relevance

Read all DRR files in .fpf/decisions/
Trace back to source evidence and hypothesis files
If foundational files changed:
- Flag the DRR as POTENTIALLY OUTDATED

Step 5: Update Baseline

Create/update .fpf/.baseline file:

# FPF Actualization Baseline
# Last actualized: 2025-01-15T16:00:00Z
commit: abc123def456

Step 6: Present Findings

Output a structured report:

## Actualization Report

**Baseline**: abc123 (2025-01-10)
**Current**: def456 (2025-01-15)
**Files Changed**: 42

### Context Drift

The following configuration files have changed:
- package.json (+5 dependencies)
- Dockerfile (base image updated)

**Action Required**: Review and update `.fpf/context.md` if constraints have changed.

### Stale Evidence (3 items)

| Evidence | Hypothesis | Changed File |
|----------|------------|--------------|
| ev-benchmark-api | api-optimization | src/api/handler.ts |
| ev-test-auth | auth-module | src/auth/login.ts |
| ev-perf-db | db-indexing | migrations/002.sql |

**Action Required**: Re-validate to refresh evidence for affected hypotheses.

### Decisions to Review (1 item)

| DRR | Affected By |
|-----|-------------|
| DRR-2025-01-10-api-design | src/api/handler.ts changed |

**Action Required**: Consider re-evaluating decision via `/fpf:propose-hypotheses`.

### Summary

- Context drift detected: YES
- Stale evidence: 3 items
- Decisions to review: 1 item

Run `/fpf:decay` for detailed freshness management.

File: .fpf/.baseline

Track the last actualization point:

# FPF Actualization Baseline
last_actualized: 2025-01-15T16:00:00Z
commit: abc123def456789
branch: main

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

FAQ

What does the actualize skill do?

Reconcile the project's FPF state with recent repository changes

How do I install actualize?

Run npx skills add https://github.com/neolabhq/context-engineering-kit --skill actualize in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/actualize/ (personal) or .claude/skills/actualize/ (project).

Which AI agents can use actualize?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is actualize safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains actualize?

It is published by neolabhq in neolabhq/context-engineering-kit. It has 1,178 recorded installs.