Codewhale Landing Workflow
codewhale-hq/Codewhale
Decides how verified work should reach main, directly, in a worktree or on an integration branch, while keeping contributor credit and respecting merge gates.
Implementation methodology for executing tasks. An agent skill from poteto/noodle.
Install Execute
$ npx skills add poteto/noodle --skill execute -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install poteto/noodle execute --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/poteto/noodle.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/execute .claude/skills/execute && 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 "execute" agent skill from https://github.com/poteto/noodle/tree/main/.agents/skills/execute into .claude/skills/execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute", 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/poteto/noodle/tree/main/.agents/skills/executeType 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 poteto/noodle --skill execute -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install poteto/noodle execute --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/poteto/noodle.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/execute .agents/skills/execute && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "execute" agent skill from https://github.com/poteto/noodle/tree/main/.agents/skills/execute into .agents/skills/execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute", 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 poteto/noodle --skill execute -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install poteto/noodle execute --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/poteto/noodle.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/execute .cursor/skills/execute && 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 "execute" agent skill from https://github.com/poteto/noodle/tree/main/.agents/skills/execute into .cursor/skills/execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute", 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/poteto/noodle.git --path .agents/skills/execute--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 poteto/noodle --skill execute -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install poteto/noodle execute --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/poteto/noodle.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/execute .gemini/skills/execute && 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 "execute" agent skill from https://github.com/poteto/noodle/tree/main/.agents/skills/execute into .gemini/skills/execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute", 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 poteto/noodle executeInstalls 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 poteto/noodle --skill execute -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/poteto/noodle.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/execute .github/skills/execute && 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 "execute" agent skill from https://github.com/poteto/noodle/tree/main/.agents/skills/execute into .github/skills/execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute", 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 poteto/noodle --skill execute -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install poteto/noodle execute --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/poteto/noodle.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/execute .opencode/skills/execute && 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 "execute" agent skill from https://github.com/poteto/noodle/tree/main/.agents/skills/execute into .opencode/skills/execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute", 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
execute- GitHub stars
- 437
- Token cost
- ~989 tokens
- SKILL.md length
- 444 words
- Files
- 3 (incl. references)
- Skills in repo
- 26
- Repo updated
- First seen
- Licence
- MIT
At a glance
Implementation methodology for executing tasks. An agent skill from poteto/noodle.
- Works in 6 steps: Scope → Decompose → Implement → …
- Tasks that involve Git worktrees
- SKILL.md covers 1. Scope, 2. Decompose, 3. Implement and 4. Verify, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Execute is an agent skill from poteto/noodle. Implementation methodology for executing tasks. Handles scoping, decomposition, worktree workflow, verification, and commit conventions. Triggers: "execute", "implement", "build this", "code this".
Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/team-execution.md` and `references/verification.md`).
It sits in Development, covering Git worktrees and Commit messages. The repository describes itself as: Orchestrate agents using skills. The licence is MIT.
When your agent uses it
- Tasks that involve Git worktrees
- Tasks that involve Commit messages
Example prompts
- “execute”
- “implement”
- “build this”
- “/execute”
Workflow steps
6 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 82d2921. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Execute loads about 989 tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 51 tokens; SKILL.md has 444 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 poteto/noodle at commit 82d2921, republished under its MIT licence (© poteto). 444 words, ~989 tokens.
Download SKILL.mdSave it as
.claude/skills/execute/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- execute
- description
- Implementation methodology for executing tasks. Handles scoping, decomposition, worktree workflow, verification, and commit conventions. Triggers: "execute", "implement", "build this", "code this".
- schedule
- When backlog items with linked plans are ready for implementation
Execute
Implementation methodology. Loads alongside the domain skill (e.g., "noodle") — this teaches process, the domain skill teaches the codebase. Operate fully autonomously. Never ask the user. Don't stop until the work is fully complete.
Track all work with Tasks (TaskCreate, TaskUpdate, TaskList). One task per decomposed change; mark in_progress when starting, completed when done.
1. Scope
Establish what needs doing:
- Plan phase: Read the assigned phase from
brain/plans/. Read the overview for scope boundaries. Invoke Skill(backlog) for project-specific context. Load domain skills listed in "Applicable skills." - Backlog item: Read the todo from
brain/todos.md. If a linked plan exists, read it. Otherwise, scope from the description. - Ad-hoc request: The user prompt is the scope. Identify affected files and packages before starting.
Output: a clear, bounded description of what changes and what doesn't.
2. Decompose
Break scope into discrete changes. Each change:
- One function/type + its tests, OR one bug fix
- Independently compilable
- One conventional commit
Single-change scopes skip decomposition.
3. Implement
Worktree First — Non-Negotiable
Never edit files on main. Multiple sessions run concurrently; editing main causes merge conflicts and lost work.
If CWD is already inside .worktrees/, use it. Otherwise: noodle worktree create <descriptive-name>
Use absolute paths or noodle worktree exec <name> <cmd>. Never cd into a worktree — if it gets removed while the shell is inside, the session dies permanently.
Commit inside the worktree. When done: noodle worktree merge <name>
Skip only when the user is interactively driving a single-agent session and explicitly chooses main.
Show full SKILL.md (200 more words)Show less
Delegation
- Self-execute: Single change, or tightly coupled changes (shared types, sequential dependencies).
- Sub-agents: 2+ independent changes touching different files. Front-load context: scope, relevant code, domain skill name.
- Team execution: 2+ parallelizable phases in a plan. See
references/team-execution.md. - Codex: Mechanical work not requiring judgment (renames, boilerplate, repetitive edits). Never for architectural decisions.
Sequential is fine when phases are tightly coupled. Before parallelizing, ask: "Does any phase's output become another phase's input?" Phases with shared type-level contracts must be sequential.
4. Verify
Run the full verification suite before committing. See references/verification.md for the complete checklist. Never commit failing code — fix and re-verify on failure.
5. Commit
<type>(<scope>): <description> with optional Refs: #<issue-ID> footer. Types: feat, fix, refactor, test, docs, chore. One commit per logical change.
6. Yield
After all changes are committed and verified, emit stage_yield:
noodle event emit --session $NOODLE_SESSION_ID stage_yield --payload '{"message": "Implemented: <brief summary>"}'Without this, the stage only completes on clean process exit — interrupted work is lost to the pipeline.
Scope Discipline
- Only change what's in scope. No defensive code, backwards-compat shims, or speculative features.
- Out-of-scope discoveries go in the quality review notes — don't change them.
- Wrong or incomplete plan/requirements: flag it in output, don't silently deviate.
Principles
Read at runtime from brain/principles/:
- [[prove-it-works]]
- [[subtract-before-you-add]]
- [[cost-aware-delegation]]
- [[guard-the-context-window]]
- [[boundary-discipline]]
- [[outcome-oriented-execution]]
© poteto, 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 2 other files (references) in .agents/skills/execute of poteto/noodle.
- SKILL.md
- references/team-execution.md
- references/verification.md
Open the folder on GitHubat commit 82d2921
Compare with similar skills
Execute 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 |
|---|---|---|---|---|---|---|
| Execute this skillpoteto/noodle | 437 | — | ~989 | Automated safety check: Pass | MIT | |
| Codewhale Landing Workflowcodewhale-hq/Codewhale | 41k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Git Committisfeng/Easydict | 15k | — | ~535 | Automated safety check: Pass | GPL-3.0 | |
| Worktree Rebase Mergetisfeng/Easydict | 15k | — | ~408 | Automated safety check: Pass | GPL-3.0 | |
| Worktrunk Git Worktree Managerjjmartres/opencode | 133 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Git Commitnex-agi/NexRL | 119 | — | ~380 | Automated safety check: Notes | Apache-2.0 |
Similar skills
Git Commit
tisfeng/Easydict
起草、创建或汇报 Angular-style 本地 Git 提交。用于明确的提交交付；分支集成使用 worktree-rebase-merge，不 push。
Worktree Rebase Merge
tisfeng/Easydict
将当前 worktree 的任务提交 rebase 到本地目标分支，并从目标 worktree 合并。用于明确要求本地集成；仅创建提交使用 git-commit。
Worktrunk Git Worktree Manager
jjmartres/opencode
Guides use of Worktrunk (wt), a CLI that makes git worktrees as easy as branches so several AI agents can work in parallel on isolated branches.
Git Commit
nex-agi/NexRL
Git commit workflow in a worktree with Python linting, formatting, and testing.
Conventional Git
samber/cc-skills
Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for GitHub and GitLab projects.
More from poteto/noodle
All 26 skills in this repoMeditate
poteto/noodle
Audit and evolve the brain vault — prune outdated content, discover cross-cutting principles, review skills for structural encoding opportunities.
Ruminate
poteto/noodle
Mine past Claude Code and Codex conversations for uncaptured patterns, corrections, and knowledge.
Ast Grep
poteto/noodle
Structural code search via ast-grep — use when code shape and element relationships matter, not just text.
Noodle
poteto/noodle
Operate the Noodle CLI — explain commands, find flags, create/edit .noodle.toml config.
Plan
poteto/noodle
Systematic planning for medium-to-large tasks. An agent skill from poteto/noodle.
Quality
poteto/noodle
Post-cook quality gate. An agent skill from poteto/noodle.
Related
Categories
Questions about Execute
What does Execute do?
Implementation methodology for executing tasks. An agent skill from poteto/noodle. Execute is an agent skill from poteto/noodle. Implementation methodology for executing tasks.
When should I use Execute?
Execute fits situations like: tasks that involve Git worktrees; tasks that involve Commit messages.
How do I install Execute in Claude Code?
Run `npx skills add poteto/noodle --skill execute -a claude-code`. Or copy the skill folder (.agents/skills/execute in poteto/noodle) into .claude/skills/execute in your project. Claude Code loads it when a task matches its description.
How do I install Execute in Codex?
Run `npx skills add poteto/noodle --skill execute -a codex`. Or copy the skill folder (.agents/skills/execute in poteto/noodle) into .agents/skills/execute in your project. Codex loads it when a task matches its description.
Can I use Execute 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 poteto/noodle --skill execute -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/execute, .gemini/skills/execute, .github/skills/execute and .opencode/skills/execute in your project.
What does Execute need to run?
SKILL.md names no scripts, command-line tools or credentials: Execute is instructions for the agent only.
Does Execute access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Execute 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 Execute use?
Execute 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 Execute use?
About 989 tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 602 tokens, read only when the agent opens those files.
What are the alternatives to Execute?
Skills that share tags, products or a category with Execute: Codewhale Landing Workflow (codewhale-hq/Codewhale, 41k stars), Git Commit (tisfeng/Easydict, 15k stars), Worktree Rebase Merge (tisfeng/Easydict, 15k stars) and Worktrunk Git Worktree Manager (jjmartres/opencode, 133 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Execute?
poteto (a GitHub user) maintains it in poteto/noodle, which has 437 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on March 19, 2026.
Source: poteto/noodle on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.