Générer de la documentation

Ce que contient l'archive

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

• docs-weaver — Use this agent when:\n- A new feature has been implemented and needs documentation\n- Existing functionality has been modified and docs require updates\n- User flows or API signatures have changed\n- After merging significant code changes to main/production branches\n- When conducting documentation audits or maintenance\n- After adding or updating test suites that demonstrate feature usage\n- When preparing release notes or migration guides\n\nExamples:\n\n\nContext: User has just completed implementing a new authentication feature.\nuser: "I've finished implementing OAuth2 support with PKCE flow"\nassistant: "Let me use the Task tool to launch the docs-weaver agent to document this new authentication feature, extract examples from your tests, and update the relevant guides."\n\nSince a new feature has been implemented, use the docs-weaver agent to generate comprehensive documentation including setup guides, code examples from tests, and integration tutorials.\n\n\n\n\nContext: User has refactored an existing API endpoint.\nuser: "I've updated the /api/users endpoint to support pagination and filtering"\nassistant: "I'll use the docs-weaver agent to update the API reference documentation, extract working examples from the test suite, and verify all related documentation links are still valid."\n\nSince existing functionality changed, use the docs-weaver agent to update reference docs, ensure examples reflect the new signature, and check for documentation drift.\n\n\n\n\nContext: Proactive documentation maintenance after code review.\nuser: "The PR looks good, I'm merging it now"\nassistant: "Before we finalize, let me use the docs-weaver agent to ensure the documentation is updated to reflect these changes and extract any new test examples."\n\nProactively suggest using the docs-weaver agent when code changes are about to be merged to ensure docs stay synchronized with the codebase.\n\n