Reconcile FPF knowledge base with git diffs and update baseline.
npx skills add https://github.com/luicabref97/sushi-jungle-web --skill fpf-actualize
Please help me install this Agent Skill. Skill: fpf:actualize Source: https://github.com/luicabref97/sushi-jungle-web/tree/main/.agents/skills/fpf-actualize Command: npx skills add https://github.com/luicabref97/sushi-jungle-web --skill fpf-actualize
Reconcile the project's Formal Project File (FPF) knowledge base with recent repository changes to surface context drift, stale evidence, and decisions that may be outdated; this reduces epistemic debt and keeps assurance cases accurate as the code evolves.
Run the fpf:actualize command to scan recent commits, flag stale evidence and decisions, and update the .fpf/.baseline file.
High-intent search queries and answers about installing and using this skill.
To detect stale evidence after a git diff, you can scan your .fpf/evidence directory for carrier references. This process flags evidence whose referenced files have changed and updates the .fpf/.baseline file for future audits.
Context drift occurs when repository changes outdate your project constraints, impacting assurance cases by increasing epistemic debt. It surfaces modifications to configuration files and highlights needed updates to .fpf/context.md.
To reconcile a Formal Project File knowledge base with recent commits, perform a git change audit against a stored baseline. This enumerates changed files, summarizes diffs, and identifies DRRs that may need review.
Yes, the fpf:actualize skill works without external dependencies. It directly analyzes git diffs against a stored baseline within your repository to validate evidence and decisions in your .fpf directory.
You should run a knowledge base actualization before starting new work or after major merges. This ensures your evidence and decisions remain valid and synchronizes the .fpf/.baseline file for future audits.
luicabref97Display FPF knowledge base status with hypothesis counts, evidence freshness, and decision records.
ccfGuide AI coding decisions with auditable hypothesis-driven reasoning and Design Rationale Records.
clearclownReview code changes for quality, security, performance, and accessibility.
jellyrockDetect broken links, invalid frontmatter paths, and stale anchors in JellyRock documentation.
