Overview
Thestandardise command provides tools for managing documentation and examples consistency across the PraisonAI project. It implements the Feature Docs/Examples Protocol (FDEP) to ensure all features have proper documentation and examples.
Commands
Check
Check for standardisation issues without making changes.
Example:
Report
Generate a detailed standardisation report.
Example:
Fix
Fix standardisation issues by creating missing artifacts.
Example:
Init
Initialise a new feature with all required artifacts.
Options:
Example:
AI
AI-powered generation of documentation and examples using LLM.Real, Runnable Examples: The AI generator creates actual working code, not templates.
Examples are verified by execution before being written - if the code doesn’t run, it won’t be saved.
Options:
Features:
- Real Examples: Generates working code with mock data, not placeholder templates
- Execution Verification: Examples are run before writing to ensure they work
- Auto-Retry: If code fails, the AI attempts to fix it (up to 2 retries)
- External Library Handling: Examples requiring external libraries are marked but still saved
Checkpoint
Create an undo checkpoint before making changes.
Example:
Undo
Undo to a previous checkpoint.
Example:
Redo
Redo after an undo operation.
Example:
Workflow Example
Exit Codes
When using--ci mode:
Performance
Connection reuse (PR #5322): Repeated invocations of
praisonai standardise no longer spawn a fresh event loop per call. Per-loop connection pools (e.g. httpx.AsyncClient) and any embedder-installed scoped_bridge() are preserved across calls, so a supervisor loop invoking this command in a tight loop won’t leak sockets or hit RuntimeError: Event loop is closed. A multi-artifact run also runs unbounded (no timeout) so a long standardisation pass is never aborted mid-flight. See run_cli_coro().
