john/claude-engineering-plugin
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

feat: migrate repo releases to manual release-please (#293)

Browse Source
This commit is contained in:
Trevin Chow
2026-03-17 17:58:13 -07:00
committed by GitHub
parent 74fb71731a
commit f47f829d81
44 changed files with 1967 additions and 801 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
plugins/compound-engineering/skills/ce-plan/SKILL.md
View File

@@ -87,7 +87,7 @@ Run these agents **in parallel** to gather local context:
- Task compound-engineering:research:learnings-researcher(feature_description)
**What to look for:**
- **Repo research:** existing patterns, CLAUDE.md guidance, technology familiarity, pattern consistency
- **Repo research:** existing patterns, AGENTS.md guidance, technology familiarity, pattern consistency
- **Learnings:** documented solutions in `docs/solutions/` that might apply (gotchas, patterns, lessons learned)
These findings inform the next step.
@@ -98,7 +98,7 @@ Based on signals from Step 0 and findings from Step 1, decide on external resear
**High-risk topics → always research.** Security, payments, external APIs, data privacy. The cost of missing something is too high. This takes precedence over speed signals.
**Strong local context → skip external research.** Codebase has good patterns, CLAUDE.md has guidance, user knows what they want. External research adds little value.
**Strong local context -> skip external research.** Codebase has good patterns, AGENTS.md has guidance, user knows what they want. External research adds little value.
**Uncertainty or unfamiliar territory → research.** User is exploring, codebase has no examples, new technology. External perspective is valuable.
@@ -125,7 +125,7 @@ After all research steps complete, consolidate findings:
- **Include relevant institutional learnings** from `docs/solutions/` (key insights, gotchas to avoid)
- Note external documentation URLs and best practices (if external research was done)
- List related issues or PRs discovered
- Capture CLAUDE.md conventions
- Capture AGENTS.md conventions
**Optional validation:** Briefly summarize findings and ask if anything looks off or missing before proceeding to planning.
@@ -611,9 +611,9 @@ Loop back to options after Simplify or Other changes until user selects `/ce:wor
## Issue Creation
When user selects "Create Issue", detect their project tracker from CLAUDE.md:
When user selects "Create Issue", detect their project tracker from AGENTS.md:
1. **Check for tracker preference** in user's CLAUDE.md (global or project):
1. **Check for tracker preference** in the user's AGENTS.md (global or project). If AGENTS.md is absent, fall back to CLAUDE.md:
- Look for `project_tracker: github` or `project_tracker: linear`
- Or look for mentions of "GitHub Issues" or "Linear" in their workflow section
@@ -633,7 +633,7 @@ When user selects "Create Issue", detect their project tracker from CLAUDE.md:
4. **If no tracker configured:**
Ask user: "Which project tracker do you use? (GitHub/Linear/Other)"
- Suggest adding `project_tracker: github` or `project_tracker: linear` to their CLAUDE.md
- Suggest adding `project_tracker: github` or `project_tracker: linear` to their AGENTS.md
5. **After creation:**
- Display the issue URL