~ / rigs / SavenkoSy / sin-flow

SavenkoSy/sin-flow

Ticket-to-PR flow for a live codebase, as a Claude Code plugin: setup, sync, ingest, plan, exec, review and learning stages.

↗ GitHub ★ 6 MIT updated 2d ago project Claude Code Claude plugin
stack: Shell
share on X
ARCHETYPE
Orchestrator
A bench of specialised subagents. The main agent mostly delegates.
CONTEXT TAX · EVERY TURN
~1.4k tokens
Featherweight · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details
Quality 3/100 Guardrails v2

Copy this rig

# review before running: this installs third-party code
$ npx degit SavenkoSy/sin-flow/agents ./rig-sin-flow/agents
$ npx degit SavenkoSy/sin-flow/skills ./rig-sin-flow/skills
$ npx degit SavenkoSy/sin-flow/hooks ./rig-sin-flow/hooks

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ npx degit SavenkoSy/sin-flow/skills/exec .claude/skills/exec
$ npx degit SavenkoSy/sin-flow/skills/ingest .claude/skills/ingest
$ npx degit SavenkoSy/sin-flow/skills/learning .claude/skills/learning
$ npx degit SavenkoSy/sin-flow/skills/plan .claude/skills/plan
$ npx degit SavenkoSy/sin-flow/skills/review .claude/skills/review
$ npx degit SavenkoSy/sin-flow/skills/setup .claude/skills/setup
$ npx degit SavenkoSy/sin-flow/skills/sync .claude/skills/sync
$ curl -fsSL --create-dirs -o .claude/agents/board.md https://raw.githubusercontent.com/SavenkoSy/sin-flow/main/agents/board.md
$ curl -fsSL --create-dirs -o .claude/agents/implementer.md https://raw.githubusercontent.com/SavenkoSy/sin-flow/main/agents/implementer.md
$ curl -fsSL --create-dirs -o .claude/agents/read-only-analyst.md https://raw.githubusercontent.com/SavenkoSy/sin-flow/main/agents/read-only-analyst.md
$ curl -fsSL --create-dirs -o .claude/agents/review-poster.md https://raw.githubusercontent.com/SavenkoSy/sin-flow/main/agents/review-poster.md
$ curl -fsSL --create-dirs -o .claude/agents/reviewer.md https://raw.githubusercontent.com/SavenkoSy/sin-flow/main/agents/reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/shipper.md https://raw.githubusercontent.com/SavenkoSy/sin-flow/main/agents/shipper.md

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(./.env.*)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(git push --force:*)",
      "Read(**/*.pem)",
      "Read(.env)",
      "Read(~/.aws/**)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Bash(rm -rf *)",
      "Bash(sudo *)",
      "Bash(sudo:*)",
      "Bash(rm -rf /)",
      "Bash(git push -f:*)",
      "Read(.env.*)",
      "Bash(git reset --hard*)",
      "Bash(rm -rf /*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(gh pr merge *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(gh pr merge:*)",
      "Bash(gh pr create *)",
      "Bash(git reset --hard:*)",
      "Bash(npm publish:*)",
      "Bash(git rebase *)"
    ]
  }
}

Skills (7)

Subagents (6)

board
model: haiku
Mechanical board work for the sin-flow:sync skill on the GitHub Projects board in tracker.board or the local adapter in tracker.adapter that a flow profile names — fetch the board, diff it against the
implementer
model: sonnet
Writes the code for ONE task of an approved plan, from a brief file, and reports back status plus a report path. Dispatched by the sin-flow:exec skill, one per task. Never spawns subagents and never r
read-only-analyst
model: sonnet
Reads code and answers one narrow question about it — source analysis for a plan, a coverage audit, a scoped re-review, a whole-branch review, or an adversarial check of someone else's finding. Cannot
review-poster
model: sonnet
Posts the user's chosen sin-flow:review findings to a GitHub PR as ONE review with event COMMENT — inline comments on lines the PR diff can take, everything else in the review body. Dispatched by `/si
reviewerRuns ONE lens of the review pipeline over a prepared review package — `context`, a finder lens (`code`, `fit`, `all` — bundles of the checklists in `lenses/`), `verify` or `settle`. Dispatched by the
shipper
model: sonnet
Mechanical gate and git work for every flow stage, in any repo that has a flow profile, so the orchestrator never runs a test suite or a git command itself. Four modes — gate (run the repo's quality g

Similar rigs

copied ✓