Add YYLO to Development Tools - #120
Merged
Merged
Conversation
Owner
|
Very interesting |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🛠️ Changes Proposed
Adds YYLO to
### Development Tools(one entry, one section, one factual line, appended at the section tail per the freshest merged adds #118/#112).yylo/yy), MIT-licensed, installable from npm as@yylo/cli.YYLO runs Pi and Codex as subagent engines inside a dedicated branch/worktree per task, wraps each task in typed task/validation/merge/release-readiness boundaries, and routes integration through a risk-based merge queue (low risk: no semantic reviewer; high risk: two sequential reviewers on one frozen candidate) with receipt-backed, hash-verified changes. It sits beside the in-section orchestrators (claude-squad, bernstein, SwarmClaw, Alfred) as the merge-governance layer: the task → isolated worktree → validation → gated-merge loop is the unit.
📈 Proof of Traction
@yylo/cli: 780 downloads in the last month — https://api.npmjs.org/downloads/point/last-month/@yylo/cli✅ Quick Check
--subagent codex), with its own model-alias table distinct from Pi's (README: "Pi and Codex do not share the same:minimapping"). YYLO drives Codex sessions as the working agents in the task loop, not just a README mention.yylo(0 hits); every phrase in the entry line is copied from the project's own README (no marketing copy).Disclosure
I'm on the team that builds YYLO; this PR (branch, entry, body) was prepared with an AI coding agent and reviewed by me before submission. Happy to adjust the section placement or description if the fit is better elsewhere.