completing

Automate feature finalization by validating tests, confirming an Approved review verdict, and then either merging locally or creating a pull request. The process also invokes auto-documentation to generate a completion artifact before marking the feature as completed.

After code review approval, the feature finalization process checks for uncommitted changes, runs the test suite, merges the branch or creates a PR, generates a completion artifact via auto-documentation, and updates the feature state to completed.

Yes, feature completion requires an Approved review verdict, a fully passing test suite, and zero uncommitted changes. It reads the active feature from its directory and validates these artifacts before allowing the finalization phase to proceed.

Yes, you can generate a completion summary automatically by invoking the auto-documentation sub-skill during the finalization phase. This produces a completion artifact and updates the feature documentation after the merge or PR creation is validated.

If uncommitted changes exist, the feature finalization process will halt because it requires a clean working directory. You must commit or discard changes before the workflow can validate tests, merge, or create a pull request.

You need an automated feature completion workflow when a feature has finished the Design, Planning, Implementation, and Review phases. It ensures final verification, branch finalization, and documentation updates are handled consistently before closing the feature.