worclaude 1.6.0 → 1.6.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (7) hide show
  1. package/package.json +1 -1
  2. package/templates/commands/commit-push-pr.md +1 -0
  3. package/templates/commands/conflict-resolver.md +1 -0
  4. package/templates/commands/end.md +1 -0
  5. package/templates/commands/sync.md +1 -0
  6. package/templates/core/claude-md.md +1 -0
  7. package/templates/skills/universal/git-conventions.md +2 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "worclaude",
3
- "version": "1.6.0",
3
+ "version": "1.6.1",
4
4
  "description": "CLI tool that scaffolds a comprehensive Claude Code workflow into any project",
5
5
  "type": "module",
6
6
  "bin": {
package/templates/commands/commit-push-pr.md CHANGED
@@ -1,4 +1,5 @@
1
1
  Determine which branch you're on, then follow the appropriate flow.
2
+ Do not add Co-Authored-By trailers or AI-generated footers to commits or PR descriptions.
2
3
 
3
4
  ## On a feature branch (feature/*, fix/*, chore/*, refactor/*)
4
5
 
package/templates/commands/conflict-resolver.md CHANGED
@@ -36,5 +36,6 @@ If anything fails, fix it.
36
36
 
37
37
  - git add -A
38
38
  - git commit -m "merge: resolve conflicts on develop"
39
+ Use exactly this message format — no trailers or Co-Authored-By lines.
39
40
 
40
41
  Do NOT push. Do NOT create a PR. The user will run /sync next.
package/templates/commands/end.md CHANGED
@@ -13,4 +13,5 @@ Do NOT update PROGRESS.md — /sync handles that on develop after merging.
13
13
  - Files that were modified
14
14
  3. git add -A
15
15
  4. git commit -m "wip: handoff for [task description]"
16
+ Use exactly this message format — no trailers or Co-Authored-By lines.
16
17
  5. git push
package/templates/commands/sync.md CHANGED
@@ -45,5 +45,6 @@ and tell the user to run /conflict-resolver first.
45
45
 
46
46
  8. git add -A
47
47
  9. git commit -m "chore: sync progress, spec, and version to [new version]"
48
+ Use exactly this message format — no trailers or Co-Authored-By lines.
48
49
  10. git push origin develop
49
50
  11. gh pr create --base main with description of what was merged
package/templates/core/claude-md.md CHANGED
@@ -42,6 +42,7 @@ See `.claude/skills/` — load only what's relevant:
42
42
  6. Use subagents to keep main context clean.
43
43
  7. Mediocre fix → scrap it, implement elegantly.
44
44
  8. Feature branches NEVER modify shared-state files. Those are updated only on develop via /sync after merging PRs. See git-conventions.md Shared-State Files for the canonical list.
45
+ 9. Never add Co-Authored-By trailers, AI attribution footers, or "Generated with" signatures to commits or PRs.
45
46
 
46
47
  ## Gotchas
47
48
  [Grows during development]
package/templates/skills/universal/git-conventions.md CHANGED
@@ -46,6 +46,7 @@ Rules:
46
46
  - No period at the end of the subject line
47
47
  - Blank line between subject and body
48
48
  - Body explains motivation, not mechanics
49
+ - Never append Co-Authored-By trailers, AI attribution lines, or "Generated with" footers
49
50
 
50
51
  ## When to Commit
51
52
 
@@ -76,6 +77,7 @@ All feature/bugfix branches are created from and merged back into `develop`. Nev
76
77
  4. PR title follows same format as commit subject: `type(scope): description`
77
78
  5. PR body includes: what changed, why, how to test, anything reviewers should know
78
79
  6. Request review if the project has reviewers configured
80
+ 7. Do not add AI-generated footers (e.g., "Generated with Claude Code") to PR descriptions
79
81
 
80
82
  ## Squash vs Merge
81
83