Skip to content
Agentmart
Submit a tool

update-extension-patch

Update an extension patch for a PR-related bug instead of editing patched output directly

Skill by mondaycomOfficial

IndexedMIT★ 4
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/mondaycom-update-extension-patch

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Update an extension patch for a PR-related bug instead of editing patched output directly

Use cases: writing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/update-extension-patch

What's inside

Skill name
update-extension-patch
Description
Update an extension patch for a PR-related bug instead of editing patched output directly
License
MIT
Instructions
61 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Update Extension Patch for PR-Related Bug

Only follow this flow when the bug is in an extension and is related to the current PR. Update the patch file rather than modifying already-patched generated output.

## Step 1: Identify the extension

Find the relevant extension config file in `.github/config/extensions/` and note:
- The extension repository URL
- The pinned commit hash (tag)
- Whether `APPLY_PATCHES` is already set

## Step 2: Clone the extension repository

```bash
git clone <extension-repo> /tmp/<extension-name>
```

## Step 3: Enable patching if needed

If the extension config does not already have `APPLY_PATCHES`, add it to the config file at `.github/config/extensions/<extension-name>`.

## Step 4: Check out the pinned commit

In the cloned extension repository:
```bash
cd /tmp/<extension-name>
git checkout <pinned-commit-hash>
```

Use the pinned commit hash found in Step 1.

## Step 5: Apply all existing patches

Apply every existing patch from `.github/patches/extensions/` for this extension, in order:
```bash
git apply /path/to/duckdb/.github/patches/extensions/<extension-name>/<patch-file>.patch
```

Make sure all existing patches apply cleanly before proceeding.

## Step 6: Make the required code changes

Edit the code in the cloned extension to fix the bug.

## Step 7: Generate a new patch

```bash
git diff > /path/to/duckdb/.github/patches/extensions/<extension-name>/fix.patch
```

## Step 8: Verify

Review the generated patch to confirm it contains only the intended changes. Replace the existing patch file if updating an existing fix, or add the new patch file if it's a new fix.

## Important

- Always apply all existing patches before making changes, so the new patch layers correctly.
- The patch must be generated against the pinned commit with all prior patches applied.
- Do not edit patched output files directly — always update the patch source.

From mondaycom/duckdb-claude, MIT.

Signals

Stars
4
Forks
1
Open issues
0
Last commit (this folder)
Mar 21, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from mondaycom

Cite this page

update-extension-patch skill. Agent Mart. https://agentmart.dev/skills/mondaycom-update-extension-patch (last updated 2026-10-24)