Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Full optimization workflow with git branch creation, commits, and optional PR.
Install Lading Optimize Submit
$ npx skills add DataDog/lading --skill lading-optimize-submit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install DataDog/lading lading-optimize-submit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/DataDog/lading.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/lading-optimize-submit .claude/skills/lading-optimize-submit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "lading-optimize-submit" agent skill from https://github.com/DataDog/lading/tree/main/.claude/skills/lading-optimize-submit into .claude/skills/lading-optimize-submit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lading-optimize-submit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/DataDog/lading/tree/main/.claude/skills/lading-optimize-submitType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add DataDog/lading --skill lading-optimize-submit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install DataDog/lading lading-optimize-submit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DataDog/lading.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/lading-optimize-submit .agents/skills/lading-optimize-submit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lading-optimize-submit" agent skill from https://github.com/DataDog/lading/tree/main/.claude/skills/lading-optimize-submit into .agents/skills/lading-optimize-submit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lading-optimize-submit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DataDog/lading --skill lading-optimize-submit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install DataDog/lading lading-optimize-submit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DataDog/lading.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/lading-optimize-submit .cursor/skills/lading-optimize-submit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lading-optimize-submit" agent skill from https://github.com/DataDog/lading/tree/main/.claude/skills/lading-optimize-submit into .cursor/skills/lading-optimize-submit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lading-optimize-submit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/DataDog/lading.git --path .claude/skills/lading-optimize-submit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add DataDog/lading --skill lading-optimize-submit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install DataDog/lading lading-optimize-submit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DataDog/lading.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/lading-optimize-submit .gemini/skills/lading-optimize-submit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lading-optimize-submit" agent skill from https://github.com/DataDog/lading/tree/main/.claude/skills/lading-optimize-submit into .gemini/skills/lading-optimize-submit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lading-optimize-submit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install DataDog/lading lading-optimize-submitInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add DataDog/lading --skill lading-optimize-submit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/DataDog/lading.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/lading-optimize-submit .github/skills/lading-optimize-submit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lading-optimize-submit" agent skill from https://github.com/DataDog/lading/tree/main/.claude/skills/lading-optimize-submit into .github/skills/lading-optimize-submit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lading-optimize-submit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DataDog/lading --skill lading-optimize-submit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install DataDog/lading lading-optimize-submit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DataDog/lading.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/lading-optimize-submit .opencode/skills/lading-optimize-submit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lading-optimize-submit" agent skill from https://github.com/DataDog/lading/tree/main/.claude/skills/lading-optimize-submit into .opencode/skills/lading-optimize-submit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lading-optimize-submit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
lading-optimize-submit- GitHub stars
- 101
- Token cost
- ~837 tokens
- SKILL.md length
- 198 words
- Files
- 2 (incl. assets)
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Full optimization workflow with git branch creation, commits, and optional PR.
- Works in 5 steps: Pre-flight → Prepare Git Environment → Hunt → …
- Tasks that involve Git workflow
- SKILL.md covers Phase 0: Pre-flight, Phase 1: Prepare Git Environment, Phase 2: Hunt and Phase 3: Create Optimization…, plus 1 more section
- Calls git and gh; reaches claude.com
What it does
Lading Optimize Submit is an agent skill from DataDog/lading, published by the product's own GitHub organization. Full optimization workflow with git branch creation, commits, and optional PR. Wraps /lading-optimize-hunt with git automation.
Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including assets.
It sits in Development, covering Git workflow. It works with Git. The repository describes itself as: A suite of data generation and load testing tools. The licence is MIT.
When your agent uses it
- Tasks that involve Git workflow
Example prompts
- “/lading-optimize-submit”
Requirements
- Pre-approved tools (allowed-tools): Bash(git:*), Bash(gh:*), Bash(cat:*), Read, Skill
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a7bb0ea. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(git:*)Bash(gh:*)Bash(cat:*)ReadSkill
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
claude.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Lading Optimize Submit loads about 837 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 198 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from DataDog/lading at commit a7bb0ea, republished under its MIT licence (© DataDog). 198 words, ~837 tokens.
Download SKILL.mdSave it as
.claude/skills/lading-optimize-submit/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- lading-optimize-submit
- description
- Full optimization workflow with git branch creation, commits, and optional PR. Wraps /lading-optimize-hunt with git automation.
- allowed-tools
- Bash(git:*), Bash(gh:*), Bash(cat:*), Read, Skill
Optimization Submit Workflow
Complete optimization workflow with git automation. This skill wraps /lading-optimize-hunt and handles:
- Git branch creation
- Git commit with formatted results
- Optional push and PR creation
Phase 0: Pre-flight
Run /lading-preflight first to ensure environment is ready.
Phase 1: Prepare Git Environment
# Ensure clean state on main
git checkout main && git pull
# Verify clean working directory
git statusSTOP if working directory is dirty. Commit or stash changes before proceeding.
Phase 2: Hunt
Run /lading-optimize-hunt.
CRITICAL: After /lading-optimize-hunt completes, you MUST return here to Phase 3.
The hunt workflow will:
- Select and analyze optimization targets
- Capture baseline benchmarks
- Implement optimization
- Run basic ci/validate check
- Invoke /lading-optimize-review (which runs post-change benchmarks and judges)
The hunt will:
- Record the verdict in
.claude/skills/lading-optimize-hunt/assets/db.yamlafter review returns
BUT the hunt does NOT:
- Run post-change benchmarks (review does this)
- Make pass/fail decisions (review does this)
- Create git branches
- Commit changes
- Push to remote
- Create PRs
Those are the responsibility of THIS skill (lading-optimize-submit).
Phase 3: Create Optimization Branch
Create a new branch and add the changes.
# Create descriptive branch name
# Format: opt/<crate>-<technique>
# Examples:
# opt/payload-cache-prealloc
# opt/throttle-avoid-clone
# opt/syslog-buffer-reuse
git checkout -b opt/<crate>-<technique>
git add .Using the template in .claude/skills/lading-optimize-submit/assets/commit-template.txt, commit the changes:
# Example:
git commit -m "opt: buffer reuse in syslog serialization
Replaced per-iteration format!() with reusable Vec<u8> buffer.
Target: lading_payload/src/syslog.rs::Syslog5424::to_bytes
Technique: buffer-reuse
Micro-benchmarks:
syslog_100MiB: +42.0% throughput (481 -> 683 MiB/s)
Macro-benchmarks (payloadtool):
Time: -14.5% (8.3 ms -> 7.1 ms)
Memory: -35.8% (6.17 MiB -> 3.96 MiB)
Allocations: -49.3% (67,688 -> 34,331)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
"Note:
- First line must be ≤50 characters (Git best practice)
- Replace {MODEL} with the actual Claude model being used (e.g., "Claude Sonnet 4.5", "Claude Opus 4.5").
Phase 4: Push and Create PR (Optional)
# Push branch to remote
git push -u origin opt/<crate>-<technique>
# Create PR using gh CLI
gh pr create \
--title "opt: <short description>" \
--body "$(cat <<'EOF'
## Summary
<What was optimized>
## Benchmark Results
### Micro-benchmarks
- <benchmark_name>: <result>
### Macro-benchmarks (payloadtool)
- Time: <-X%> (<old> ms -> <new> ms)
- Memory: <-X%> (<old> MiB -> <new> MiB)
- Allocations: <-X%> (<old> -> <new>)
## Validation
- [x] ci/validate passes
- [x] Kani proofs pass (or N/A: <reason>)
- [x] Determinism verified
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"© DataDog, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (assets) in .claude/skills/lading-optimize-submit of DataDog/lading.
- SKILL.md
- assets/commit-template.txt
Open the folder on GitHubat commit a7bb0ea
Compare with similar skills
Lading Optimize Submit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lading Optimize Submit this skillDataDog/lading | 101 | — | ~837 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Migrate Internal Package into GhostTryGhost/Ghost | 55k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
Git Merge Conflict Resolver
tailcallhq/forgecode
Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.
More from DataDog/lading
- Official
Lading Optimize Find Target
DataDog/lading
Finds a valid optimization target in lading. An agent skill from DataDog/lading.
- Official
Lading Optimize Hunt
DataDog/lading
Coordinates optimization attempts. An agent skill from DataDog/lading.
- Official
Lading Optimize Review
DataDog/lading
Reviews optimization patches using a 5-persona peer review system.
- Official
Lading Preflight
DataDog/lading
Environment validation checklist. An agent skill from DataDog/lading.
- Official
Release
DataDog/lading
Prepare a lading release. An agent skill from DataDog/lading.
Related
Works with
Categories
Questions about Lading Optimize Submit
What does Lading Optimize Submit do?
Full optimization workflow with git branch creation, commits, and optional PR. Lading Optimize Submit is an agent skill from DataDog/lading, published by the product's own GitHub organization. Full optimization workflow with git branch creation, commits, and optional PR.
When should I use Lading Optimize Submit?
Lading Optimize Submit fits situations like: tasks that involve Git workflow.
How do I install Lading Optimize Submit in Claude Code?
Run `npx skills add DataDog/lading --skill lading-optimize-submit -a claude-code`. Or copy the skill folder (.claude/skills/lading-optimize-submit in DataDog/lading) into .claude/skills/lading-optimize-submit in your project. Claude Code loads it when a task matches its description.
How do I install Lading Optimize Submit in Codex?
Run `npx skills add DataDog/lading --skill lading-optimize-submit -a codex`. Or copy the skill folder (.claude/skills/lading-optimize-submit in DataDog/lading) into .agents/skills/lading-optimize-submit in your project. Codex loads it when a task matches its description.
Can I use Lading Optimize Submit in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DataDog/lading --skill lading-optimize-submit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lading-optimize-submit, .gemini/skills/lading-optimize-submit, .github/skills/lading-optimize-submit and .opencode/skills/lading-optimize-submit in your project.
What does Lading Optimize Submit need to run?
Going by SKILL.md and its folder, Lading Optimize Submit needs the command-line tools its instructions call (git and gh). Its frontmatter pre-approves these tools: Bash(git:*), Bash(gh:*), Bash(cat:*), Read, Skill.
Does Lading Optimize Submit access the network?
SKILL.md names 1 domain. In commands or code: claude.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Lading Optimize Submit safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Lading Optimize Submit use?
Lading Optimize Submit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Lading Optimize Submit use?
About 837 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Lading Optimize Submit?
Skills that share tags, products or a category with Lading Optimize Submit: Finishing a Development Branch (obra/superpowers, 296k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Migrate Internal Package into Ghost (TryGhost/Ghost, 55k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lading Optimize Submit?
DataDog (a GitHub organization, an official publisher) maintains it in DataDog/lading, which has 101 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 30, 2026.
Source: DataDog/lading on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.