cekrause/workflows

Workflows turns recurring engineering tasks into portable procedures with clear boundaries, evidence-based completion, and no required project framework.

Repository (opens in a new tab)

Git worktrees · Commits and pull requests · Read-only reviews · Developer documentation · HTML artifacts · Independent skills

Product

Engineering agents repeatedly need to prepare worktrees, organize commits, draft pull requests, review changes, maintain documentation, and explain systems visually. Workflows packages those jobs as six focused skills that can be installed and used independently.

Each skill defines the evidence needed to finish its task and preserves the repository's existing choices. Host branch prefixes, user instructions, pull request templates, and documentation structures remain authoritative.

What I built

I built standalone workflows for worktree planning and lifecycle checks, cohesive commits, truthful pull request drafts, evidence-backed reviews, developer documentation, and portable HTML artifacts.

The review workflow stays read-only unless a fix is also requested. Commit and publication actions remain explicit, and every skill can run without Harness; an optional, narrow integration can add continuity context when Harness is already installed.

Engineering choices

Each skill guides the agent’s use of existing Git, file, and review tools. The package contains instructions without a custom runtime or bundled executable scripts. Those instructions define the outcome, relevant decisions, and completion evidence while leaving technical judgment to the agent and user.

Writers preserve existing files and layouts by default. Review findings require concrete evidence, documentation claims are checked against source, and HTML reports keep their essential assets embedded so they can open directly from disk.