finish-feature-remove

To finalize a feature removal, run cargo fix and cargo fmt to clean the codebase, execute the full test suite, verify no orphaned references remain, and automate PR creation via gh CLI for review.

The best way to automate PR creation after feature removal is to run pre-commit quality checks, execute full tests with automated fixes, update documentation, and use gh CLI to push commits and open a pull request.

Yes, finishing a feature removal requires running cargo fix and cargo fmt as pre-commit quality checks to ensure the codebase remains clean and properly formatted before pushing to the remote repository.

Yes, feature removal cleanup integrates end-to-end with verifuzz-like pipelines to validate the removed feature, run full tests, verify orphaned references, and ensure production readiness before merging the pull request.

To verify documentation and tests before merging, execute the full test suite with automated fixes, confirm no orphaned references remain, check that documentation is updated, and validate test success before opening a pull request.

Checking for orphaned references when removing a feature ensures that no lingering code points to the deleted functionality, preventing compilation errors and runtime failures before committing and pushing the final pull request.