Atomic Workflows Registry

Installable workflow recipes for Atomic.

Prerequisites  ·  Install  ·  Select workflows  ·  Workflows  ·  Customize  ·  Contribute  ·  Docs

---

atomic-workflows is a small registry package for Atomic. It ships TypeScript workflow definitions.

The workflows here are concrete developer-job recipes for analysis, review, security validation, implementation planning, reporting, and workflow chaining. Some are intentionally read-only; others demonstrate how one workflow can hand off to another workflow for active implementation.

Use this repository out of the box to run focused code reviews, gate security risk, turn implementation intent into approved specs, and study the same patterns as starting points for your own Atomic workflows.

Prerequisites

• Atomic installed and configured.

Install the registry

Download/install the registry globally for your user:

atomic install git:github.com/bastani-inc/atomic-workflows

Install locally for one project:

atomic install git:github.com/bastani-inc/atomic-workflows -l

-l writes the package entry to project settings (.atomic/settings.json). Without -l, Atomic writes to user settings (~/.atomic/agent/settings.json).

Update this registry

To update atomic-workflows without updating any other Atomic packages you have installed, run:

atomic update git:github.com/bastani-inc/atomic-workflows

If you installed a pinned ref such as git:github.com/bastani-inc/[email protected], Atomic skips it during package updates. Remove the ref or reinstall with an unpinned source to follow the latest version.

Enable selected workflows only

By default, Atomic loads every workflow exported by this registry. To load only the workflows you want, edit your Atomic settings after installation and add a workflows allowlist to this package entry.

Choose the settings file based on where you installed the registry:

• Project install (atomic install ... -l): .atomic/settings.json
• Global/user install: ~/.atomic/agent/settings.json

For example, this configuration enables only review-board and security-gate from atomic-workflows:

{
  "packages": [
    {
      "source": "git:github.com/bastani-inc/atomic-workflows",
      "workflows": [
        "workflows/review-board/index.ts",
        "workflows/security-gate/index.ts"
      ]
    }
  ]
}

Use workflow paths relative to the package root, such as workflows/review-board/index.ts. You can also exclude specific workflows with !workflows/<name>/index.ts. See workflows/README.md for more filter examples.

Registry workflows

These workflows are provided by this registry package after installation. See workflows/README.md for the current workflow index, details, and settings filter examples.

• babysit-pr: bounded PR shepherding through review feedback, inline threads, mergeability, and observed CI (empty checks are not green) with a structured preflight classifier before checkout, hard poll_timeout sleep caps, known-head, parseable receipts, trusted shell-capable remediation that can run tests/package scripts/git/gh only when routed, clean-workspace checks, and post-remediation PR-state syncing/reporting.
• review-board: read-only multi-specialist review synthesis.
• security-gate: read-only local security risk gate.
• descent, codebase-migration, and spec-driven-development: implementation, migration, and spec workflow recipes.

Customize these workflow recipes

These workflows are deliberately readable TypeScript recipes, not black boxes. Copy one into your project or your own workflow package and adapt the inputs, prompts, stages, parallel specialists, validation policy, and output format.

For full guidance on building and distributing custom workflows, see the Atomic workflows documentation. You can also ask Atomic to create a workflow for you.

Good starting points:

• Triage: issue routers, repro scouts, ownership maps.
• Testing gates: flake labs, migration plans, release smoke matrices.
• Review boards: domain-specific reviewers, API councils, cross-repo checks.
• Security: service-specific threat deltas, release gates, dependency review.
• Release/incident: changelog checks, rollout readiness, timeline reconstruction.

Contributing workflows

Have a workflow that could help others? Community submissions are welcome. See CONTRIBUTING.md for workflow contribution guidelines, directory structure, testing expectations, and authoring references.