devlyn-cli 1.1.0 → 1.1.2

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 CHANGED
@@ -6,9 +6,9 @@
6
6
  <img alt="DEVLYN" src="assets/logo.svg" width="540" />
7
7
  </picture>
8
8
 
9
- ### The Skills & Commands Toolkit for Claude Code
9
+ ### Context Engineering & Harness Engineering Toolkit for Claude Code
10
10
 
11
- **Ship better code with battle-tested AI workflows — debugging, code review, UI design, product specs, and more.**
11
+ **Structured prompts, agent orchestration, and automated pipelines — debugging, code review, UI design, product specs, and more.**
12
12
 
13
13
  [![npm version](https://img.shields.io/npm/v/devlyn-cli.svg)](https://www.npmjs.com/package/devlyn-cli)
14
14
  [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
@@ -24,13 +24,26 @@
24
24
 
25
25
  [Claude Code](https://docs.anthropic.com/en/docs/claude-code) is powerful out of the box — but teams need **consistent, repeatable workflows**. Without shared conventions, every developer prompts differently, reviews differently, and debugs differently.
26
26
 
27
- devlyn-cli solves this by installing a curated `.claude/` configuration into any project:
27
+ devlyn-cli solves this with two complementary engineering approaches:
28
+
29
+ ### Context Engineering
30
+
31
+ Structured prompts and role-based instructions that shape _what the AI knows and how it thinks_ for each task.
28
32
 
29
33
  - **16 slash commands** for debugging, code review, UI design, documentation, and more
30
34
  - **5 core skills** that activate automatically based on conversation context
31
- - **Agent team workflows** that spawn specialized AI teammates for complex tasks
35
+ - **Agent team workflows** that spawn specialized AI teammates with role-specific expertise
32
36
  - **Product & feature spec templates** for structured planning
33
- - **Commit conventions** for consistent git history
37
+
38
+ ### Harness Engineering
39
+
40
+ Pipeline orchestration that controls _how agents execute_ — permissions, state management, multi-phase workflows, and cross-model evaluation.
41
+
42
+ - **`/devlyn:auto-resolve`** — 8-phase automated pipeline (build → evaluate → fix loop → simplify → review → security → clean → docs)
43
+ - **`bypassPermissions` mode** for autonomous subagent execution
44
+ - **File-based state machine** — agents communicate via `.claude/done-criteria.md` and `EVAL-FINDINGS.md`
45
+ - **Git checkpoints** at each phase for rollback safety
46
+ - **Cross-model evaluation** via `--with-codex` flag (OpenAI Codex as independent evaluator)
34
47
 
35
48
  **Zero dependencies. One command. Works with any project.**
36
49
 
package/bin/devlyn.js CHANGED
@@ -521,10 +521,29 @@ async function init(skipPrompts = false) {
521
521
  }
522
522
  }
523
523
  if (!settings.env) settings.env = {};
524
+ // Auto-allow pipeline files so auto-resolve doesn't prompt for permission
525
+ if (!settings.permissions) settings.permissions = {};
526
+ if (!settings.permissions.allow) settings.permissions.allow = [];
527
+ const pipelinePermissions = [
528
+ 'Write:.claude/done-criteria.md',
529
+ 'Write:.claude/EVAL-FINDINGS.md',
530
+ 'Edit:.claude/done-criteria.md',
531
+ 'Edit:.claude/EVAL-FINDINGS.md',
532
+ ];
533
+ let settingsChanged = false;
534
+ for (const perm of pipelinePermissions) {
535
+ if (!settings.permissions.allow.includes(perm)) {
536
+ settings.permissions.allow.push(perm);
537
+ settingsChanged = true;
538
+ }
539
+ }
524
540
  if (!settings.env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS) {
525
541
  settings.env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS = '1';
542
+ settingsChanged = true;
543
+ }
544
+ if (settingsChanged) {
526
545
  fs.writeFileSync(settingsPath, JSON.stringify(settings, null, 2) + '\n');
527
- log(' → settings.json (agent teams enabled)', 'dim');
546
+ log(' → settings.json (agent teams + pipeline permissions)', 'dim');
528
547
  }
529
548
 
530
549
  // Install agents for other detected CLIs
@@ -26,7 +26,9 @@ $ARGUMENTS
26
26
  Codex examples: `--with-codex` (both), `--with-codex evaluate`, `--with-codex review`
27
27
  If no flags are present, use defaults.
28
28
 
29
- 3. Announce the pipeline plan:
29
+ 3. **If `--with-codex` is enabled**: Read `references/codex-integration.md` and run the "PRE-FLIGHT CHECK" section to verify Codex MCP server availability before proceeding.
30
+
31
+ 4. Announce the pipeline plan:
30
32
  ```
31
33
  Auto-resolve pipeline starting
32
34
  Task: [extracted task description]
@@ -6,6 +6,27 @@ Codex is accessed via `mcp__codex-cli__*` MCP tools (provided by codex-mcp-serve
6
6
 
7
7
  ---
8
8
 
9
+ ## PRE-FLIGHT CHECK
10
+
11
+ Before starting the pipeline, verify the Codex MCP server is available by calling `mcp__codex-cli__ping`.
12
+
13
+ - **If ping succeeds**: continue normally.
14
+ - **If ping fails or `mcp__codex-cli__ping` tool is not found**: warn the user and ask how to proceed:
15
+ ```
16
+ ⚠ Codex MCP server not detected. --with-codex requires codex-mcp-server.
17
+
18
+ To install:
19
+ npm i -g @openai/codex
20
+ claude mcp add codex-cli -- npx -y codex-mcp-server
21
+
22
+ Options:
23
+ [1] Continue without --with-codex (Claude-only evaluation/review)
24
+ [2] Abort pipeline
25
+ ```
26
+ If the user chooses [1], disable `--with-codex` and continue. If [2], stop.
27
+
28
+ ---
29
+
9
30
  ## PHASE 2-CODEX: CROSS-MODEL EVALUATE
10
31
 
11
32
  Run after the Claude evaluator (Phase 2) completes, only if `--with-codex` includes `evaluate` or `both`.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "devlyn-cli",
3
- "version": "1.1.0",
3
+ "version": "1.1.2",
4
4
  "description": "Claude Code configuration toolkit for teams",
5
5
  "bin": {
6
6
  "devlyn": "bin/devlyn.js"