actualize

Name: actualize
Author: NeoLabHQ

845installs132forks

How to install actualize?

neolabhq/context-engineering-kit/actualize

$npx -y skills add NeoLabHQ/context-engineering-kit --skill actualize

Installs into the current project.

Summary

Reconcile the project's FPF state with recent repository changes

Files · 1

View on GitHub

SKILL.md

1	# Actualize Knowledge Base
2
3	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.
4
5	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).
6
7	## Action (Run-Time)
8
9	### Step 1: Check Git Changes
10
11	Run git commands to identify changes since last actualization:
12
13	```bash
14	# Get current commit hash
15	git rev-parse HEAD
16
17	# Check for changes since last known baseline
18	# (Read .fpf/.baseline file if it exists, otherwise use initial commit)
19	git diff --name-only <baseline_commit> HEAD
20
21	# List all changed files
22	git diff --stat <baseline_commit> HEAD
23	```
24
25	### Step 2: Analyze Report for Context Drift
26
27	1. Review changed files for core project configuration:
28	- `package.json`, `go.mod`, `Cargo.toml`, `requirements.txt`
29	- `Dockerfile`, `docker-compose.yml`
30	- `.env.example`, config files
31
32	2. If configuration files changed:
33	- Re-read project structure (README, config files)
34	- Compare detected context with `.fpf/context.md`
35	- Present diff to user
36
37	3. Ask user if they want to update `context.md`
38
39	### Step 3: Analyze Report for Evidence Staleness (Epistemic Debt)
40
41	1. Read all evidence files in `.fpf/evidence/`
42	2. Check `carrier_ref` field in each evidence file
43	3. Cross-reference with changed files from git diff
44	4. If a referenced file changed:
45	- Flag the evidence as STALE
46	- Note which hypothesis is affected
47
48	### Step 4: Analyze Report for Decision Relevance
49
50	1. Read all DRR files in `.fpf/decisions/`
51	2. Trace back to source evidence and hypothesis files
52	3. If foundational files changed:
53	- Flag the DRR as POTENTIALLY OUTDATED
54
55	### Step 5: Update Baseline
56
57	Create/update `.fpf/.baseline` file:
58
59	```
60	# FPF Actualization Baseline
61	# Last actualized: 2025-01-15T16:00:00Z
62	commit: abc123def456
63	```
64
65	### Step 6: Present Findings
66
67	Output a structured report:
68
69	```markdown
70	## Actualization Report
71
72	Baseline: abc123 (2025-01-10)
73	Current: def456 (2025-01-15)
74	Files Changed: 42
75
76	### Context Drift
77
78	The following configuration files have changed:
79	- package.json (+5 dependencies)
80	- Dockerfile (base image updated)
81
82	Action Required: Review and update `.fpf/context.md` if constraints have changed.
83
84	### Stale Evidence (3 items)
85
86	\| Evidence \| Hypothesis \| Changed File \|
87	\|----------\|------------\|--------------\|
88	\| ev-benchmark-api \| api-optimization \| src/api/handler.ts \|
89	\| ev-test-auth \| auth-module \| src/auth/login.ts \|
90	\| ev-perf-db \| db-indexing \| migrations/002.sql \|
91
92	Action Required: Re-validate to refresh evidence for affected hypotheses.
93
94	### Decisions to Review (1 item)
95
96	\| DRR \| Affected By \|
97	\|-----\|-------------\|
98	\| DRR-2025-01-10-api-design \| src/api/handler.ts changed \|
99
100	Action Required: Consider re-evaluating decision via `/fpf:propose-hypotheses`.
101
102	### Summary
103
104	- Context drift detected: YES
105	- Stale evidence: 3 items
106	- Decisions to review: 1 item
107
108	Run `/fpf:decay` for detailed freshness management.
109	```
110
111	## File: .fpf/.baseline
112
113	Track the last actualization point:
114
115	```yaml
116	# FPF Actualization Baseline
117	last_actualized: 2025-01-15T16:00:00Z
118	commit: abc123def456789
119	branch: main
120	```
121
122	## When to Run
123
124	- Before starting new work: Ensure knowledge base is current
125	- After major changes: Sync evidence with code changes
126	- Weekly maintenance: Part of regular hygiene
127	- Before decisions: Ensure evidence is still valid

People who liked this also viewed

6 picks

Type

lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026382k16k
lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026382k16k
lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026380k16k
lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026380k16k
lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026330k16k
lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026227k16k

actualize

845installs132forks

View on GitHub

How to install actualize?

neolabhq/context-engineering-kit/actualize

$npx -y skills add NeoLabHQ/context-engineering-kit --skill actualize

Installs into the current project.

Summary

Reconcile the project's FPF state with recent repository changes

Files · 1

View on GitHub

SKILL.md

1	# Actualize Knowledge Base
2
3	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.
4
5	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).
6
7	## Action (Run-Time)
8
9	### Step 1: Check Git Changes
10
11	Run git commands to identify changes since last actualization:
12
13	```bash
14	# Get current commit hash
15	git rev-parse HEAD
16
17	# Check for changes since last known baseline
18	# (Read .fpf/.baseline file if it exists, otherwise use initial commit)
19	git diff --name-only <baseline_commit> HEAD
20
21	# List all changed files
22	git diff --stat <baseline_commit> HEAD
23	```
24
25	### Step 2: Analyze Report for Context Drift
26
27	1. Review changed files for core project configuration:
28	- `package.json`, `go.mod`, `Cargo.toml`, `requirements.txt`
29	- `Dockerfile`, `docker-compose.yml`
30	- `.env.example`, config files
31
32	2. If configuration files changed:
33	- Re-read project structure (README, config files)
34	- Compare detected context with `.fpf/context.md`
35	- Present diff to user
36
37	3. Ask user if they want to update `context.md`
38
39	### Step 3: Analyze Report for Evidence Staleness (Epistemic Debt)
40
41	1. Read all evidence files in `.fpf/evidence/`
42	2. Check `carrier_ref` field in each evidence file
43	3. Cross-reference with changed files from git diff
44	4. If a referenced file changed:
45	- Flag the evidence as STALE
46	- Note which hypothesis is affected
47
48	### Step 4: Analyze Report for Decision Relevance
49
50	1. Read all DRR files in `.fpf/decisions/`
51	2. Trace back to source evidence and hypothesis files
52	3. If foundational files changed:
53	- Flag the DRR as POTENTIALLY OUTDATED
54
55	### Step 5: Update Baseline
56
57	Create/update `.fpf/.baseline` file:
58
59	```
60	# FPF Actualization Baseline
61	# Last actualized: 2025-01-15T16:00:00Z
62	commit: abc123def456
63	```
64
65	### Step 6: Present Findings
66
67	Output a structured report:
68
69	```markdown
70	## Actualization Report
71
72	Baseline: abc123 (2025-01-10)
73	Current: def456 (2025-01-15)
74	Files Changed: 42
75
76	### Context Drift
77
78	The following configuration files have changed:
79	- package.json (+5 dependencies)
80	- Dockerfile (base image updated)
81
82	Action Required: Review and update `.fpf/context.md` if constraints have changed.
83
84	### Stale Evidence (3 items)
85
86	\| Evidence \| Hypothesis \| Changed File \|
87	\|----------\|------------\|--------------\|
88	\| ev-benchmark-api \| api-optimization \| src/api/handler.ts \|
89	\| ev-test-auth \| auth-module \| src/auth/login.ts \|
90	\| ev-perf-db \| db-indexing \| migrations/002.sql \|
91
92	Action Required: Re-validate to refresh evidence for affected hypotheses.
93
94	### Decisions to Review (1 item)
95
96	\| DRR \| Affected By \|
97	\|-----\|-------------\|
98	\| DRR-2025-01-10-api-design \| src/api/handler.ts changed \|
99
100	Action Required: Consider re-evaluating decision via `/fpf:propose-hypotheses`.
101
102	### Summary
103
104	- Context drift detected: YES
105	- Stale evidence: 3 items
106	- Decisions to review: 1 item
107
108	Run `/fpf:decay` for detailed freshness management.
109	```
110
111	## File: .fpf/.baseline
112
113	Track the last actualization point:
114
115	```yaml
116	# FPF Actualization Baseline
117	last_actualized: 2025-01-15T16:00:00Z
118	commit: abc123def456789
119	branch: main
120	```
121
122	## When to Run
123
124	- Before starting new work: Ensure knowledge base is current
125	- After major changes: Sync evidence with code changes
126	- Weekly maintenance: Part of regular hygiene
127	- Before decisions: Ensure evidence is still valid

People who liked this also viewed

6 picks

Type