Actualize
Skill Verified ActiveReconcile the project's FPF state with recent repository changes
To keep the project's First Principles Framework (FPF) knowledge base synchronized with evolving code, ensuring assurance cases remain current and decisions are based on up-to-date evidence.
Features
- Reconciles FPF state with Git repository changes
- Audits for context drift in configuration files
- Identifies stale evidence referencing changed files
- Flags outdated decisions potentially affected by foundational changes
- Updates a baseline commit for future comparisons
Use Cases
- Ensuring assurance cases are always up-to-date with project code
- Identifying and addressing knowledge gaps caused by code evolution
- Maintaining a reliable foundation for decision-making based on current project state
- Automating the synchronization of project reality with its documented FPF state
Non-Goals
- Automatically updating FPF state without user review
- Performing code refactoring or direct code modifications
- Managing FPF state outside of the specified `.fpf/` directory
Versioning
- info:Release ManagementThe repository has a `pushedAt` date indicating recent activity, but no explicit versioning like tags or a manifest version is evident. Install instructions reference a specific commit/branch implicitly.
Installation
First, add the marketplace
/plugin marketplace add NeoLabHQ/context-engineering-kit/plugin install fpf@context-engineering-kitQuality Score
VerifiedTrust Signals
Similar Extensions
Status
100Display the current state of the FPF knowledge base
Project Session Manager
100Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions
Sync Profiles
100Use when the user wants to list, create, switch, delete, compare, or inspect config sync profiles.
Using Git Worktrees
100Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Unslop Commit
100Rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50), imperative mood. Body only when "why" isn't obvious from the subject. Use when user says "humanize commit", "de-slop commit message", "make this commit sound human", "/unslop-commit", "/commit", "write a commit", or pastes a draft commit to clean up. Auto-triggers when staging changes.
Rule Effectiveness Analysis
100Analyze which rules are actively used vs inert. Detect coverage gaps. Recommend pruning to reduce token consumption.