public/chiche-plugins
Watch
1
0
Fork
You've already forked chiche-plugins
 0
Code Issues Pull requests Activity Actions

Rename task-python suite to taskpy; orchestrate stops at good-to-merge #7

Merged
jerome merged 3 commits from refactor/rename-taskpy-x into main 2026-06-25 08:48:51 +03:00
Conversation 2 Commits 3 Files changed 11 +255 -221
claude commented 2026-06-25 08:45:48 +03:00
Collaborator
Copy link

Renames the task-python plugin suite to taskpy and changes how taskpy-orchestrate handles the merge step.

Changes

1. Rename task-python → taskpy

  • Plugin dir, all four skills (taskpy-new / -implement / -orchestrate / -review), every internal reference, marketplace.json, plugin.json, and README.md. Zero task-python strings remain.

2. taskpy-orchestrate stops at good-to-merge — a human always merges

  • Step 5 is split into two phases:
    • Phase A — catch the branch up to the default branch (pre-merge prep), print "PR ready to merge", then stop. The skill never runs gh/fj pr merge.
    • Phase B — only after the user confirms the merge landed: fast-forward the default branch, tick any umbrella, remove the worktree, surface dependents.
  • Description, Overview, Quick Reference, Common Mistakes, AskUserQuestion gates, and test-fix-loop.md updated to match.

3. Worktrees now live inside the repo

  • worktree-and-branches.md: worktree base moved from a sibling dir to <repo_path>/.worktrees/<slug>, with a .gitignore step so they never pollute the main checkout.

🤖 Generated with Claude Code

Renames the `task-python` plugin suite to `taskpy` and changes how `taskpy-orchestrate` handles the merge step. ## Changes **1. Rename `task-python` → `taskpy`** - Plugin dir, all four skills (`taskpy-new` / `-implement` / `-orchestrate` / `-review`), every internal reference, `marketplace.json`, `plugin.json`, and `README.md`. Zero `task-python` strings remain. **2. `taskpy-orchestrate` stops at good-to-merge — a human always merges** - Step 5 is split into two phases: - **Phase A** — catch the branch up to the default branch (pre-merge prep), print "PR ready to merge", then **stop**. The skill never runs `gh/fj pr merge`. - **Phase B** — only after the user confirms the merge landed: fast-forward the default branch, tick any umbrella, remove the worktree, surface dependents. - Description, Overview, Quick Reference, Common Mistakes, AskUserQuestion gates, and `test-fix-loop.md` updated to match. **3. Worktrees now live inside the repo** - `worktree-and-branches.md`: worktree base moved from a sibling dir to `<repo_path>/.worktrees/<slug>`, with a `.gitignore` step so they never pollute the main checkout. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
refactor(taskpy-x): rename task-python suite to taskpy-x; orchestrate stops at good-to-merge
All checks were successful
gitleaks / gitleaks (pull_request) Successful in 3s
Details
c9c944c3d3 
Rename the task-python plugin and all four skills (new/implement/
orchestrate/review) to taskpy-x, including every internal reference,
the marketplace manifest, plugin manifest, and README.

Behavior changes in taskpy-x-orchestrate: it no longer merges. It
drives the PR to good-to-merge (tests green, review passed, branch
current with the default branch) and stops -- a human always performs
the merge. Post-merge cleanup (fast-forward, umbrella tick, worktree
removal) runs only after the user confirms the merge landed (Step 5
Phase A ready gate, Phase B cleanup).

Worktree convention moved inside the repo: worktrees now live at
<repo_path>/.worktrees/<slug> (was a sibling dir), with a .gitignore
step so they never pollute the main checkout.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
claude changed title from Rename task-python suite to taskpy-x; orchestrate stops at good-to-merge to Rename task-python suite to taskpy; orchestrate stops at good-to-merge 2026-06-25 08:47:23 +03:00
refactor: use taskpy prefix (taskpy-new/implement/orchestrate/review), not taskpy-x
All checks were successful
gitleaks / gitleaks (pull_request) Successful in 3s
Details
e1e5cea1ca 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jerome approved these changes 2026-06-25 08:48:26 +03:00
Dismissed
jerome approved these changes 2026-06-25 08:48:44 +03:00
jerome merged commit 7261f55de8 into main 2026-06-25 08:48:51 +03:00
Sign in to join this conversation.
Reviewers
No reviewers
jerome
Labels
Clear labels   
bug
Something is not working

  
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
help wanted
Need some help

  
invalid
Something is wrong

  
question
More information is needed

  
wontfix
This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
public/chiche-plugins!7
No description provided.