lading-optimize-submit

The lading-optimize-submit skill serves as the final, critical step in the lading project's performance optimization pipeline. It is designed for software engineers and performance analysts working on the DataDog agent or related high-performance Rust services. This skill bridges the gap between successful experimentation and version control integration, ensuring that validated performance gains are cleanly documented and upstreamed using standardized git practices.

After completing an optimization hunt and peer review, users invoke this skill to finalize their contributions. It automates the boilerplate tasks associated with submitting technical improvements, allowing developers to focus on the performance characteristics of their code rather than the mechanics of branch management and pull request templating. This ensures consistency across the repository's optimization efforts.

• Automates the creation of standardized git branches following the opt/<crate>-<technique> naming convention.

• Generates structured, compliant git commits using a pre-defined template that includes micro-benchmark and macro-benchmark results.

• Facilitates the creation of GitHub Pull Requests using the gh CLI, populated with comprehensive performance summaries and validation status.

• Wraps the preceding lading-optimize-hunt workflow to maintain strict adherence to project performance-first design goals.

• Enforces best practices for commit messages, including character limits and descriptive metadata.

• Prerequisites: Ensure the workspace is clean and that the /lading-preflight and /lading-optimize-hunt skills have been executed beforehand.

• Inputs: Relies on localized performance data recorded in .claude/skills/lading-optimize-hunt/assets/db.yaml and template files in .claude/skills/lading-optimize-submit/assets/.

• Expected Output: A pushed remote branch and an open pull request ready for final review.

• Constraints: The skill necessitates a clean git working state; it will halt execution if pending changes or unstaged modifications are detected.

• Performance standards: All submissions must uphold the lading project's requirements for determinism and lack of runtime panics, as dictated by existing ADRs.