dev-workflows
Advanced tools
+1
-1
| { | ||
| "name": "dev-workflows", | ||
| "version": "0.1.2", | ||
| "version": "0.1.3", | ||
| "type": "module", | ||
@@ -5,0 +5,0 @@ "description": "CLI that compiles developer rules into editor-specific config files", |
+18
-4
@@ -5,2 +5,4 @@ # dev-workflows | ||
| AI coding tools (Claude Code, Cursor, Gemini CLI) each use different config files for project rules. dev-workflows lets you define rules once in YAML and compile them to each tool's native format. No duplication, no drift. | ||
| ## Quick start | ||
@@ -12,2 +14,4 @@ | ||
| Requires Node.js >= 22. | ||
| ## Usage | ||
@@ -21,2 +25,16 @@ | ||
| ## What it generates | ||
| Running `devw compile` produces tool-specific files with your rules between markers: | ||
| ```md | ||
| <!-- BEGIN dev-workflows --> | ||
| - Never use `any`. Use `unknown` when the type is truly unknown. | ||
| - Always declare explicit return types on exported functions. | ||
| - Prefer union types over enums. Use `as const` objects when you need runtime values. | ||
| <!-- END dev-workflows --> | ||
| ``` | ||
| Content outside the markers is preserved — your manual notes stay intact. | ||
| ## Available blocks | ||
@@ -44,8 +62,4 @@ | ||
| ## Documentation | ||
| Full specification: [docs/CLI_SPEC.md](docs/CLI_SPEC.md) | ||
| ## License | ||
| MIT |
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
117349
0.55%62
29.17%