review-incan-source-quality

Review touched .incn sources to evaluate readability, idiomatic structure, and dogfooding integrity, ensuring module layout, docstrings, and public API align with the current style guidelines.

Incan code reads like well-written Python when it uses Pythonic naming conventions, idiomatic module organization, and clear documentation, avoiding anti-patterns and Rust-shaped scaffolding that reduce maintainability.

Check if your Incan stdlib examples meet style guidelines by auditing the touched source for module structure, ownership, documentation, and public API quality to ensure a Pythonic experience for users.

Yes, you can review user-provided Incan snippets for anti-patterns by assessing readability, idiomatic structure, and public surface quality, generating suggestions for Pythonic naming and organization improvements.

Yes, the Incan readability audit validates source ownership and module structure, ensuring that touched .incn files align with the current Incan capability baseline and maintain dogfooding integrity throughout the public API.

Run a readability assessment on Incan language-surface implementations when you need to verify that touched sources avoid anti-patterns, maintain idiomatic structure, and provide a Pythonic experience aligned with the capability baseline.