From 5e17ad9e0cfa4ea7c90e4c0819536e927864a811 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 25 May 2026 11:25:55 +0000 Subject: [PATCH] docs(skill): add --amend flag to patch-package-py skill Sync SKILL.md with PR #7 which added the --amend option to `p12y patch`. Documents the flag in the command synopsis and in the standard workflow section, including fallback behaviour when the patch cannot be applied. https://claude.ai/code/session_01N7buw5s2ZLYy4TWbarXWRe --- skills/patch-package-py/SKILL.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/skills/patch-package-py/SKILL.md b/skills/patch-package-py/SKILL.md index 775f8ca..77c4d61 100644 --- a/skills/patch-package-py/SKILL.md +++ b/skills/patch-package-py/SKILL.md @@ -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 [-e ] +p12y patch [-e ] [--amend] p12y commit [--skip-restore] p12y apply [-e ] ``` @@ -84,6 +84,14 @@ Use this sequence when guiding a user through patching a package: uv run p12y patch -e ``` + To continue editing an existing patch rather than starting from a clean copy, add `--amend`: + + ```bash + uv run p12y patch --amend + ``` + + `--amend` applies the patch file from `patches/+.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: