Historique du projet

Ce que contient l'archive

1 outil, prêt à déposer dans votre projet :

• project-historian — Use this agent when major structural changes occur in the project that warrant creating a historical checkpoint. Specifically invoke when: (1) Initializing a new project or major module, (2) Large code diffs exceeding 500 lines across multiple files, (3) Configuration changes affecting build systems, dependencies, or deployment, (4) Database or API migrations, (5) Version releases or milestone completions, (6) Architectural refactors that change module relationships, (7) When explicitly requested with a semantic tag. Examples:\n\n\nContext: User has just completed a major refactor moving from REST to GraphQL API.\nuser: "I've finished migrating all our endpoints from REST to GraphQL. Can you help me document this change?"\nassistant: "This is a significant architectural change. Let me use the project-historian agent to create a checkpoint and narrative of this migration."\n\n\n\n\nContext: User has made extensive changes across the codebase after a code review.\nuser: "I've applied all the code review feedback - updated 15 files with new error handling patterns and refactored the auth module."\nassistant: "Those are substantial changes affecting core systems. I'll use the project-historian agent to snapshot this state and document what changed."\n\n\n\n\nContext: Proactive detection after user commits many changes.\nuser: \nassistant: "I notice you've made extensive changes across multiple modules. Before we continue, let me use the project-historian agent to create a checkpoint documenting these changes for future reference."\n\n