miko.quick_catchup

To update business logic documentation from code changes, you can analyze git diffs to generate proposal documents and synchronize business rules with high-level design files. This approach keeps documentation aligned with multiple changesets in your codebase.

Keeping high-level design documents in sync with codebase updates requires analyzing git diffs to identify modified business rules. You can then generate proposal documents that reflect the current state of the business logic.

Git diff analysis extracts code changes across multiple changesets to identify impacted business logic. It then maps these code modifications to existing business rules and high-level design documents, proposing necessary textual updates.

Yes, you can generate proposal documents for specific code changes by providing a capability name and an optional diff source. The system processes the git diff to produce targeted business logic documentation updates.

You should use automated documentation generation for business logic when your codebase undergoes frequent updates across multiple changesets. It ensures high-level design documents and business rules remain accurate without manual markdown editing.

Yes, miko.quick_catchup processes markdown documents to update business rules and high-level designs. It reads existing markdown files and modifies them based on analyzed git diffs to maintain accurate business logic documentation.