From fpf
Audits git changes against FPF knowledge base to detect config drift, stale evidence, outdated decisions, and update baseline in .fpf/. Useful after repo updates in FPF projects.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fpf:actualizeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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).
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
Review changed files for core project configuration:
package.json, go.mod, Cargo.toml, requirements.txtDockerfile, docker-compose.yml.env.example, config filesIf configuration files changed:
.fpf/context.mdAsk user if they want to update context.md
.fpf/evidence/carrier_ref field in each evidence file.fpf/decisions/Create/update .fpf/.baseline file:
# FPF Actualization Baseline
# Last actualized: 2025-01-15T16:00:00Z
commit: abc123def456
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.
Track the last actualization point:
# FPF Actualization Baseline
last_actualized: 2025-01-15T16:00:00Z
commit: abc123def456789
branch: main
npx claudepluginhub neolabhq/context-engineering-kit --plugin fpfGenerates FPF evidence freshness reports identifying stale/expired items and supports refresh, deprecate, or waive actions for governance.
Audits project configuration and documentation for drift, staleness, and broken references. Scans CLAUDE.md files, configs, plugin manifests, and knowledge files.
Checks whether project documentation is up-to-date after code changes by scanning git diffs and reporting stale or missing docs.