worclaude 1.3.0 → 1.3.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "worclaude",
-  "version": "1.3.0",
+  "version": "1.3.2",
   "description": "CLI tool that scaffolds a comprehensive Claude Code workflow into any project",
   "type": "module",
   "bin": {

package/src/core/merger.js

@@ -133,10 +133,7 @@ async function mergeSkills(projectRoot, existingScan, variables, report, selecti
   // Generated skill: agent-routing.md
   const routingFilename = 'agent-routing.md';
   const skillsDir = path.join('.claude', 'skills');
-  const routingContent = buildAgentRoutingSkill(
-    selections.selectedAgents,
-    selections.projectTypes
-  );
+  const routingContent = buildAgentRoutingSkill(selections.selectedAgents, selections.projectTypes);
 
   if (existingScan.existingSkills.includes(routingFilename)) {
     await writeFile(

package/src/generators/agent-routing.js

@@ -8,7 +8,7 @@ import { AGENT_REGISTRY } from '../data/agent-registry.js';
  * @returns {string} - complete markdown content for agent-routing.md
  */
 export function buildAgentRoutingSkill(selectedAgentNames, _projectTypes) {
-  const allAgents = [...UNIVERSAL_AGENTS, ...selectedAgentNames];
+  const allAgents = [...new Set([...UNIVERSAL_AGENTS, ...selectedAgentNames])];
 
   const automaticAgents = [];
   const manualAgents = [];

package/templates/commands/commit-push-pr.md

@@ -2,8 +2,14 @@
 2. Write a clear, conventional commit message
 3. Push to the current branch
 4. Create a PR with:
-   - Clear title
+   - Clear title matching conventional commit format
    - Description of changes
    - Testing done
    - Any notes for reviewers
+
+Branch targeting rules:
+
+- Feature/bugfix branches → PR targets `develop` (`gh pr create --base develop`)
+- When on `develop` → PR targets `main` (`gh pr create --base main`) — release merges only
+
 Use `gh pr create` for PR creation.

package/templates/skills/universal/git-conventions.md

@@ -56,13 +56,26 @@ Commit after each logical unit of work:
 
 Don't batch unrelated changes into one commit. Don't commit broken code.
 
+## Branching Strategy
+
+```
+feature-branch ──PR──▶ develop ──PR──▶ main (release)
+```
+
+- `develop` — active development. Contributors fork, branch from `develop`, and PR back to `develop`.
+- `main` — production releases. Maintainer-only, merged from `develop`.
+- `gh-pages` — auto-deployed docs. Maintainer-only.
+
+All feature/bugfix branches are created from and merged back into `develop`. Never PR directly to `main`.
+
 ## PR Workflow
 
 1. Push your branch
-2. Create PR with `gh pr create`
-3. PR title follows same format as commit subject: `type(scope): description`
-4. PR body includes: what changed, why, how to test, anything reviewers should know
-5. Request review if the project has reviewers configured
+2. Create PR with `gh pr create --base develop` (feature/bugfix branches target `develop`)
+3. When on `develop`, PR targets `main`: `gh pr create --base main` (release merges only)
+4. PR title follows same format as commit subject: `type(scope): description`
+5. PR body includes: what changed, why, how to test, anything reviewers should know
+6. Request review if the project has reviewers configured
 
 ## Squash vs Merge