actualize — Claude Code skill: what it does, how to install
Checks an FPF knowledge base against Git changes and flags evidence or decisions that may need review. Use it before new work or after repository changes.
npx skills add NeoLabHQ/context-engineering-kit --skill actualize -a claude-codeWhat actualize does
actualize compares the .fpf/ knowledge base with Git changes after the commit stored in .fpf/.baseline. When that baseline file is absent, it starts from the repository’s initial commit. It examines changed-file names and statistics, then checks project configuration against .fpf/context.md.
The skill reads evidence in .fpf/evidence/, inspects each carrier_ref, and flags records tied to changed files. It also follows links from files in .fpf/decisions/ to their evidence and hypotheses to identify decisions that may need review. It then updates .fpf/.baseline and produces a structured report.
Git and an .fpf/ directory are required because the skill compares repository changes with that knowledge base. Set up FPF before relying on this check.
What it helps with
- compare an FPF knowledge base with Git history
- flag evidence linked to changed files
- identify decisions that may need re-evaluation
- write a new baseline to
.fpf/.baseline
Example prompts for the agent
- Run the actualize skill for the current repository.
- Use actualize to find stale evidence after code changes.
- Run actualize and update
.fpf/.baselineafter the review.
How to install actualize
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill actualize -a claude-code2Manually: put the files in place
~/.claude/skills/actualize/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/actualize/
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill actualize -a codex2Manually: put the files in place
.agents/skills/actualize/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill actualize -a cursor2Manually: put the files in place
.cursor/skills/actualize/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install NeoLabHQ/context-engineering-kit actualize2Manually: put the files in place
.github/skills/actualize/SKILL.md1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill actualize -a gemini-cli2Platform CLI
gemini skills install https://github.com/NeoLabHQ/context-engineering-kit --path skills/actualizeManually: put the files in place
.devin/skills/actualize/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill actualize -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about actualize
How do I install actualize in Claude Code?
Run npx skills add NeoLabHQ/context-engineering-kit --skill actualize -a claude-code, then run npx skills add NeoLabHQ/context-engineering-kit --skill actualize -a claude-code again. The skill file is placed at ~/.claude/skills/actualize/SKILL.md.
What does actualize do?
It compares the FPF knowledge base with Git changes, checks whether evidence is still current, and reviews related decisions. It writes an updated baseline after the check.
Which files does actualize inspect?
It checks changes to configuration such as package.json, go.mod, Cargo.toml, requirements.txt, Dockerfile, docker-compose.yml, and .env.example. It also reads records in .fpf/evidence/ and .fpf/decisions/.