Skip to content

Add --amend flag to patch command for continuing edits #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nomyfan merged 1 commit into from
May 25, 2026
+9 −1
Merged

Add --amend flag to patch command for continuing edits #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion skills/patch-package-py/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ compatibility: Requires Python >= 3.9, uv, git, and the patch utility. Windows u
The CLI has three commands:

```bash
p12y patch <package> [-e <env-path>]
p12y patch <package> [-e <env-path>] [--amend]
p12y commit <edit-path> [--skip-restore]
p12y apply [-e <env-path>]
```
Expand Down Expand Up @@ -84,6 +84,14 @@ Use this sequence when guiding a user through patching a package:
uv run p12y patch <package> -e <env-path>
```

To continue editing an existing patch rather than starting from a clean copy, add `--amend`:

```bash
uv run p12y patch <package> --amend
```

`--amend` applies the patch file from `patches/<package-name>+<version>.patch` (if it exists) onto the fresh workspace so your previous changes are already present when you open the editor. If the patch cannot be applied cleanly, `p12y` falls back to a clean workspace and logs a warning.

4. Edit files inside the path printed by `p12y patch`.
5. Commit the edited package copy from the project root:

Expand Down
Loading