aif-transfer

Transfer anonymized prevention lessons from another AI Factory project into current skill-context.

1.1k|96|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/lee-to/ai-factory --skill aif-transfer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-transfer
Source: https://github.com/lee-to/ai-factory/tree/main/skills/aif-transfer
Command: npx skills add https://github.com/lee-to/ai-factory --skill aif-transfer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When starting a new project similar to a previous one, hard-won lessons captured in the old project's fix patches are lost. This Skill reuses those prevention lessons without leaking the source project's identity, paths, or proprietary identifiers into your current project.

Core Features & Use Cases

  • Privacy-safe knowledge transfer: Reads fix patches from another AI Factory project's .ai-factory/patches directory, extracts prevention points, and anonymizes all source identifiers before use.
  • Relevance gating: Keeps only lessons verified against the current project's stack, architecture, and code, rejecting generic or inapplicable advice.
  • Delegated evolution workflow: Feeds sanitized candidates into the existing /aif-evolve workflow, which applies approved improvements to skill-context and writes an evolution log.
  • Use Case: You built a Laravel API project where patches captured lessons about validation and queue handling. Starting a new Laravel project, run the transfer to reuse those prevention rules without exposing the old client's name, repository, or file paths.

Quick Start

Run /aif-transfer with the path to a reference AI Factory project, for example /aif-transfer "/path/to/reference-project" all, then approve the proposed improvements.

Frequently Asked Questions about aif-transfer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I transfer lessons from another AI Factory project?

Run /aif-transfer with the source project path, for example /aif-transfer "/path/to/reference-project" all. The skill reads the source project's fix patches, filters relevant prevention lessons, anonymizes them, and runs the /aif-evolve workflow for your approval.

Does aif-transfer copy patches into my current project?

No. Source patches are never copied into the current project's patches directory. Only anonymized prevention lessons that pass relevance and privacy checks are proposed through /aif-evolve, and nothing is written without your explicit approval.

Can the source project be modified during a transfer?

No. The source project is strictly read-only for the entire run. The skill only reads the source config, description, architecture, and patch markdown files, and never calls Write or Edit on any path under the source root.

What happens if no lessons are relevant to my project?

If no prevention candidate survives the relevance gate, the skill reports only the analyzed and rejected counts and stops. No evolution log is created and no skill-context files are changed.

How does aif-transfer protect the source project's privacy?

It builds an in-memory denylist of source names, paths, URLs, and identifiers, rewrites candidates with neutral roles or verified current-project equivalents, and scans all outputs before and after writes. Source identity never appears in artifacts or reports.

What are the prerequisites for running aif-transfer?

The current project must be initialized with /aif and have a description artifact, the aif-evolve skill must be available, and the source project must contain a .ai-factory directory with at least one patch file.