worclaude 1.6.1 → 1.7.0
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.
- package/README.md +2 -2
- package/package.json +1 -1
- package/src/data/agents.js +1 -0
- package/templates/commands/review-changes.md +20 -0
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Worclaude
|
|
2
2
|
|
|
3
|
-
> One command.
|
|
3
|
+
> One command. Best practices baked in. Your Claude Code environment, production-ready.
|
|
4
4
|
|
|
5
5
|
[](https://www.npmjs.com/package/worclaude)
|
|
6
6
|
[](LICENSE)
|
|
@@ -10,7 +10,7 @@
|
|
|
10
10
|
|
|
11
11
|
[Full Documentation](https://sefaertunc.github.io/Worclaude/) · [Interactive Demo](https://sefaertunc.github.io/Worclaude/demo/) · [npm](https://www.npmjs.com/package/worclaude)
|
|
12
12
|
|
|
13
|
-
Worclaude scaffolds a complete Claude Code workflow into any project in seconds. It implements all [
|
|
13
|
+
Worclaude scaffolds a complete Claude Code workflow into any project in seconds. It implements all [tips by Boris Cherny](https://www.howborisusesclaudecode.com/) — the creator of Claude Code at Anthropic — as a reusable, upgradable scaffold. One `init` command gives you 23 agents, 12 slash commands, 13 skills, hooks, permissions, and a CLAUDE.md template tuned for your tech stack. Whether you're starting fresh or adding structure to an existing project, Worclaude handles the setup so you can focus on building.
|
|
14
14
|
|
|
15
15
|
---
|
|
16
16
|
|
package/package.json
CHANGED
package/src/data/agents.js
CHANGED
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
Review changed code for reuse, quality, and efficiency.
|
|
2
|
+
|
|
3
|
+
CRITICAL: This is a READ-ONLY review. You MUST NOT edit any files.
|
|
4
|
+
You MUST NOT make any commits. You MUST NOT stage changes.
|
|
5
|
+
Only analyze and report.
|
|
6
|
+
|
|
7
|
+
1. Read recent changes (git diff HEAD~1 or staged changes)
|
|
8
|
+
2. Check for:
|
|
9
|
+
- Duplicated code or missed reuse opportunities
|
|
10
|
+
- Unnecessary complexity or abstraction
|
|
11
|
+
- Inconsistency with project patterns
|
|
12
|
+
- CLAUDE.md compliance issues
|
|
13
|
+
3. Report findings as a prioritized table:
|
|
14
|
+
|
|
15
|
+
| Finding | Category | Action |
|
|
16
|
+
|---------|----------|--------|
|
|
17
|
+
| [what] | [type] | Fix / Skip — [reason] |
|
|
18
|
+
|
|
19
|
+
The user will decide which findings to act on and apply fixes themselves.
|
|
20
|
+
Do NOT apply any fixes. Do NOT touch any files. REPORT ONLY.
|