Menu
Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.
Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
npx skills add https://github.com/christophacham/agent-skills-library --skill fpfactualizeO comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.
Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.
Baseado na classificação ocupacional SOC
Exibindo SKILL.md
| name | fpf:actualize |
| description | Reconcile the project's FPF state with recent repository changes |
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).
Run git commands to identify changes since last actualization:
# 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
Review changed files for core project configuration:
package.json, go.mod, Cargo.toml, requirements.txtDockerfile, docker-compose.yml.env.example, config filesIf configuration files changed:
.fpf/context.mdAsk user if they want to update context.md
.fpf/evidence/carrier_ref field in each evidence file.fpf/decisions/Create/update .fpf/.baseline file:
# FPF Actualization Baseline
# Last actualized: 2025-01-15T16:00:00Z
commit: abc123def456
Output a structured report:
## 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.
Track the last actualization point:
# FPF Actualization Baseline
last_actualized: 2025-01-15T16:00:00Z
commit: abc123def456789
branch: main