lading-optimize-submit

Automate git branches, commits, and PRs for lading optimization workflows.

98|16|Updated Mar 3, 2021
One-click install
npx skills add https://github.com/DataDog/lading --skill lading-optimize-submit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lading-optimize-submit
Source: https://github.com/DataDog/lading/tree/main/.claude/skills/lading-optimize-submit
Command: npx skills add https://github.com/DataDog/lading --skill lading-optimize-submit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill automates the end-to-end optimization workflow for lading projects by orchestrating git branches, commits, and optional PRs based on the results of /lading-optimize-hunt.

Core Features & Use Cases

  • Git automation: creates opt/<crate>-<technique> branches, commits using the provided template, and pushes PRs when requested.
  • Benchmark integration: captures baseline and post-change results into db.yaml.
  • Workflow orchestration: coordinates preflight, hunt, and review steps to deliver repeatable optimization cycles.

Quick Start

Run /lading-optimize-submit after /lading-preflight and /lading-optimize-hunt to finalize changes and optionally open a PR.

Frequently Asked Questions about lading-optimize-submit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git branching and pull requests for optimization workflows?

Automate optimization submission by orchestrating git branches, commits, and optional PRs. The workflow creates opt/<crate>-<technique> branches, commits using a provided template, and pushes results to a pull request.

How do I record baseline and post-change benchmark results into a yaml database?

Record benchmark results into db.yaml by capturing baseline and post-change metrics during the optimization workflow. The automation ensures results are captured after re-benchmarking code modifications.

Do I need a clean git workspace before running an optimization submission?

Yes, optimization submission requires a clean workspace before starting. The workflow orchestrates preflight checks, hunt execution, and review steps to deliver repeatable optimization cycles.

What is the workflow for finalizing code changes after an optimization hunt?

Finalize optimization changes by running the submission skill after preflight and hunt steps. It coordinates benchmarking, creates git commits using the commit template, and optionally opens a pull request.

Can I use a custom commit template for automated optimization pull requests?

The workflow uses the commit template located at assets/commit-template.txt to standardize git commits. It applies this template when creating commits on opt/<crate>-<technique> branches during optimization cycles.

Why does my optimization submission workflow require preflight and hunt steps first?

The submission workflow depends on prior preflight and hunt steps to establish baseline benchmarks and identify code changes. Running it ensures repeatable optimization cycles by validating the workspace and capturing results.