mirror of
https://github.com/nodnarbnitram/claude-code-extensions.git
synced 2026-09-14 18:36:21 +08:00
1ac816cc29
## Summary - convert the marketplace packages into self-contained plugin installs with local `agents/`, `skills/`, `commands/`, and `hooks/` content - replace the old `triage-workflow` path with the new `linear` skill and ship a dedicated `cce-linear` plugin for Linear-backed ticket and PR workflows - remove the unfinished `cce-auto-blog` plugin so this PR stays focused on the plugin infrastructure redo ## What Changed - added `scripts/sync_plugin_packages.py` to generate package manifests and sync plugin-local assets from the shared `.claude/` source tree - updated `.claude-plugin/marketplace.json` and per-plugin manifests for 19 packages, including new `cce-linear` and `cce-tauri` entries - materialized packaged plugin assets under `plugins/*` so marketplace installs no longer depend on repo-root `.claude` paths - rewired Linear commands to use the `linear` skill wrapper scripts and removed hardcoded workspace-specific Linear URLs - refreshed root and plugin README files to match the packaged layout and current plugin inventory ## Verification - `python3 -m py_compile scripts/sync_plugin_packages.py install_extensions.py .claude/skills/linear/scripts/*.py` - `python3 scripts/sync_plugin_packages.py` - validated plugin JSON/manifests and `cce-linear` package wiring - confirmed no `axios-hq` or `triage-workflow` references remain in the `.claude` Linear sources --------- Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
28 lines
917 B
Bash
Executable File
28 lines
917 B
Bash
Executable File
#!/bin/bash
|
|
# UserPromptSubmit hook that forces explicit skill evaluation
|
|
|
|
cat <<'EOF'
|
|
INSTRUCTION: MANDATORY SKILL ACTIVATION SEQUENCE
|
|
|
|
Step 1 - EVALUATE (do this in your response):
|
|
For each skill in <available_skills>, state: [skill-name] - YES/NO - [reason]
|
|
|
|
Step 2 - ACTIVATE (do this immediately after Step 1):
|
|
IF any skills are YES → Use Skill(skill-name) tool for EACH relevant skill NOW
|
|
IF no skills are YES → State "No skills needed" and proceed
|
|
|
|
Step 3 - IMPLEMENT:
|
|
Only after Step 2 is complete, proceed with implementation.
|
|
|
|
CRITICAL: You MUST call Skill() tool in Step 2. Do NOT skip to implementation.
|
|
The evaluation (Step 1) is WORTHLESS unless you ACTIVATE (Step 2) the skills.
|
|
|
|
Example of correct sequence:
|
|
- linear: YES - need to create or update a Linear ticket before continuing the workflow
|
|
|
|
[Then IMMEDIATELY use Skill() tool:]
|
|
> Skill(linear)
|
|
|
|
[THEN and ONLY THEN start implementation]
|
|
EOF
|