chore(marketplace): add publish-plugin, rewrite init.sh, cleanup obsolete plugins
- Add publish-plugin: marketplace publish + Feishu bot notification - Rewrite init.sh: SSE-first, fixed prod API, remove env selection - Update CLAUDE.md, README.md, claude-config.yaml - Update skills: req-plugin, req-prd-plugin, pull-request-plugin - Delete sync-skills.sh (obsolete) - Delete deprecated plugins: skills-ops/*, skills-projects/*, old skills-dev/req duplicates - Regenerate marketplace.json (27 plugins) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -199,3 +199,50 @@ One paragraph explaining the motivation.
|
||||
↓
|
||||
tea pr merge 42
|
||||
```
|
||||
|
||||
## Finishing a Branch
|
||||
|
||||
Verify tests pass, then create PR. Use after implementation is complete.
|
||||
|
||||
**Core principle:** Verify tests → Create PR → Done.
|
||||
|
||||
### Process
|
||||
|
||||
1. **Verify Tests** — Run project's test suite before creating PR:
|
||||
```bash
|
||||
npm test / cargo test / pytest / go test ./... / mvn test
|
||||
```
|
||||
- Tests fail → Stop, show failures, fix first. Cannot proceed.
|
||||
- Tests pass → Continue to step 2.
|
||||
|
||||
2. **Create PR** — Use `/pr create` (checks for existing PR, avoids duplicates). Report PR URL.
|
||||
|
||||
3. **Cleanup Worktree** (if applicable):
|
||||
```bash
|
||||
git worktree list | grep $(git branch --show-current)
|
||||
# If in worktree, ask user to confirm removal
|
||||
git worktree remove <worktree-path>
|
||||
```
|
||||
|
||||
**Never:** Create PR with failing tests. Skip test verification. Force-push without request.
|
||||
|
||||
## Plan Execution
|
||||
|
||||
Load plan → create branch → execute tasks in batches → report for review between batches.
|
||||
|
||||
### Process
|
||||
|
||||
1. **Load Plan**: Read plan file, review critically, raise concerns before starting
|
||||
2. **Setup Branch**: Use `/pr start` or manual `git checkout -b <type>/<name> origin/main`
|
||||
3. **Execute Batch**: Default 3 tasks per batch, mark in_progress → completed
|
||||
4. **Report**: Show implementation + verification output. Say: "Ready for feedback."
|
||||
5. **Continue**: Apply feedback, execute next batch, repeat
|
||||
6. **Complete**: Use "Finishing a Branch" workflow above
|
||||
|
||||
### Stop Conditions
|
||||
|
||||
- Hit blocker (missing dependency, test fails, instruction unclear)
|
||||
- Plan has critical gaps preventing starting
|
||||
- Verification fails repeatedly
|
||||
|
||||
**Ask for clarification rather than guessing.**
|
||||
|
||||
Reference in New Issue
Block a user