Agent skill

Actualize

by NeoLabHQ in NeoLabHQ/context-engineering-kit

Reconcile the project's FPF state with recent repository changes

GPL-3.0Auto-check passedKnowledge Management

Install Actualize

skills CLI
$ npx skills add NeoLabHQ/context-engineering-kit --skill actualize -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NeoLabHQ/context-engineering-kit actualize --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NeoLabHQ/context-engineering-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/actualize .claude/skills/actualize && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
actualize
GitHub stars
1.8k
Token cost
~932 tokens
SKILL.md length
277 words
Files
1
Skills in repo
57
Repo updated
First seen
Licence
GPL-3.0

At a glance

Reconcile the project's FPF state with recent repository changes

  • Works in 6 steps: Check Git Changes → Analyze Report for Context Drift → Analyze Report for Evidence Staleness… → …
  • Knowledge Management work in your project
  • SKILL.md covers Action (Run-Time), File: .fpf/.baseline and When to Run
  • Calls git

What it does

Actualize is an agent skill from NeoLabHQ/context-engineering-kit. Reconcile the project's FPF state with recent repository changes

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Knowledge Management. It works with Git. The repository describes itself as: Hand-crafted Claude Code Skills focused on improving agent results quality. Compatible with OpenCode, Cursor, Antigravity, Gemini CLI, and others. Includes CodeRabbit open-source… The licence is GPL-3.0.

When your agent uses it

  • Knowledge Management work in your project

Example prompts

  • “/actualize”

Requirements

  • Docker

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Check Git Changes
  2. Analyze Report for Context Drift
  3. Analyze Report for Evidence Staleness (Epistemic Debt)
  4. Analyze Report for Decision Relevance
  5. Update Baseline
  6. Present Findings

What it can do on your machine

Read from SKILL.md and the folder at commit 23e2428. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Actualize loads about 932 tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 277 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~932

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NeoLabHQ/context-engineering-kit at commit 23e2428, republished under its GPL-3.0 licence (© NeoLabHQ). 277 words, ~932 tokens.

Download SKILL.mdSave it as .claude/skills/actualize/SKILL.md (or your agent's skills folder).
name
actualize
description
Reconcile the project's FPF state with recent repository changes

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:

bash
# 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
  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 carrier_ref 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:

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

Output a structured report:

markdown
## 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:

yaml
# 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

© NeoLabHQ, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/actualize of NeoLabHQ/context-engineering-kit.

Open the folder on GitHubat commit 23e2428

Compare with similar skills

Actualize next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Actualize compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Actualize this skillNeoLabHQ/context-engineering-kit1.8k—~932Automated safety check: PassGPL-3.0
Logseq Review Workflow Evallogseq/logseq45k—~1kAutomated safety check: PassAGPL-3.0
LLM WikiCharlesHoskinson/sevenlayer116—~1.5kAutomated safety check: PassCustom licence
Open Pagepricklywiggles/niamos192—~939Automated safety check: PassNone
Memex Synciamtouchskyer/memex143—~533Automated safety check: PassMIT
Turingdb GraphClawBio/ClawBio1.2k1 repos~4.2kAutomated safety check: PassMIT

Similar skills

  • Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…

    45k GitHub stars~1k tokensUpdated today
    Knowledge ManagementAuto-check passed
  • LLM Wiki

    CharlesHoskinson/sevenlayer

    Builds and maintains a persistent, interlinked Obsidian-compatible markdown knowledge wiki in a git repo via three operations — ingest a source into linked pages, answer a question from the…

    116 GitHub stars~1.5k tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed
  • Open Page

    pricklywiggles/niamos

    Search for and open a page in Obsidian by name, description, or keywords.

    192 GitHub stars~939 tokensUpdated 3 mo ago
    Knowledge ManagementAuto-check passed
  • Memex Sync

    iamtouchskyer/memex

    Sync Zettelkasten cards across devices via git. An agent skill from iamtouchskyer/memex.

    143 GitHub stars~533 tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed
  • Turingdb Graph

    ClawBio/ClawBio

    Build, query, and analyse biomedical knowledge graphs in TuringDB, a columnar graph database with git-like versioning.

    1.2k GitHub starsUsed in 1 repo~4.2k tokens
    Knowledge ManagementAuto-check passed
  • Xs Diary

    karaage0703/ai-assistant-workspace

    日記スキル。日次の振り返りとNotion連携. An agent skill from karaage0703/ai-assistant-workspace.

    136 GitHub stars~496 tokensUpdated 17 days ago
    Knowledge ManagementAuto-check passed

More from NeoLabHQ/context-engineering-kit

All 57 skills in this repo
  • Git Notes

    NeoLabHQ/context-engineering-kit

    A skill your agent uses when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or supplementing commit messages post-hoc - provides…

    1.8k GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Load PR Comments

    NeoLabHQ/context-engineering-kit

    A skill your agent uses to load open/unresolved PR review comments then aggregate them as tasks in .specs/comments/.md for parallel agents to fix.

    1.8k GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Prompt Engineering

    NeoLabHQ/context-engineering-kit

    A skill your agent uses when you writing commands, hooks, skills for Agent, or prompts for sub agents or any other LLM interaction, including optimizing prompts, improving LLM outputs, or designing…

    1.8k GitHub stars~4.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Multi Agent Patterns

    NeoLabHQ/context-engineering-kit

    Design multi-agent architectures for complex tasks. An agent skill from NeoLabHQ/context-engineering-kit.

    1.8k GitHub starsUsed in 6 repos~6k tokens
    Auto-check passed
  • Review PR

    NeoLabHQ/context-engineering-kit

    Review an existing GitHub pull request and post inline review comments on its diff.

    1.8k GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Subagent Driven Development

    NeoLabHQ/context-engineering-kit

    A skill your agent uses when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or…

    1.8k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Questions about Actualize

What does Actualize do?

Reconcile the project's FPF state with recent repository changes. Actualize is an agent skill from NeoLabHQ/context-engineering-kit.

When should I use Actualize?

Actualize fits situations like: knowledge Management work in your project.

How do I install Actualize in Claude Code?

Run `npx skills add NeoLabHQ/context-engineering-kit --skill actualize -a claude-code`. Or copy the skill folder (skills/actualize in NeoLabHQ/context-engineering-kit) into .claude/skills/actualize in your project. Claude Code loads it when a task matches its description.

How do I install Actualize in Codex?

Run `npx skills add NeoLabHQ/context-engineering-kit --skill actualize -a codex`. Or copy the skill folder (skills/actualize in NeoLabHQ/context-engineering-kit) into .agents/skills/actualize in your project. Codex loads it when a task matches its description.

Can I use Actualize in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NeoLabHQ/context-engineering-kit --skill actualize -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/actualize, .gemini/skills/actualize, .github/skills/actualize and .opencode/skills/actualize in your project.

What does Actualize need to run?

Going by SKILL.md and its folder, Actualize needs the command-line tools its instructions call (git). Our summary lists: Docker.

Does Actualize access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Actualize safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Actualize use?

Actualize is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Actualize use?

About 932 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Actualize?

Skills that share tags, products or a category with Actualize: Logseq Review Workflow Eval (logseq/logseq, 45k stars), LLM Wiki (CharlesHoskinson/sevenlayer, 116 stars), Open Page (pricklywiggles/niamos, 192 stars) and Memex Sync (iamtouchskyer/memex, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Actualize?

NeoLabHQ (a GitHub organization) maintains it in NeoLabHQ/context-engineering-kit, which has 1,750 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on August 26, 2026.

Source: NeoLabHQ/context-engineering-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.