burkeholland

Ultralight Orchestration

A minimal multi-agent system with an orchestrator, a planner, a coder, and a designer working together providing orchestration between Claude, Codex and Gemini.

Instructions

Install all agents listed below into VS Code Insiders...

Title	Type	Description

OmerFarukOruc

AI Coding Agent Guidelines (claude.md)

These rules define how an AI coding agent should plan, execute, verify, communicate, and recover when working in a real codebase. Optimize for correctness, minimalism, and developer experience.

---

Operating Principles (Non-Negotiable)

• Correctness over cleverness: Prefer boring, readable solutions that are easy to maintain.
• Smallest change that works: Minimize blast radius; don't refactor adjacent code unless it meaningfully reduces risk or complexity.

arilivigni

American Football Game Stats Tracker & Report Generator

Build a comprehensive web application for tracking statistics during an American football game and generating detailed reports at the end.

Football Rules Reference

Basic Game Structure

• Field: 100 yards long with 10-yard end zones at each end
• Teams: 11 players per side on the field
• Quarters: Four 15-minute quarters

robandpdx

Migration Guide from Gerrit to GitHub

Scope of the document

This document provides the steps involved in migrating source code from Gerrit to GitHub. The CI/CD setup part is currently out of scope of this document.

Introduction

Below is a guided procedure to ensure a migration from Gerrit to GitHub.

Migration steps

The following steps act as high-level phases when implementing a migration project:

n1snt

Note

I’ve written a newer optimized 2026 version of this guide with a faster setup using Zinit + Starship and improved plugin loading.

This version avoids slow shell startups and works better with modern Zsh setups.

Updated guide: https://gist.github.com/n1snt/2cccc8aa5f7b645a7628d3512c70deb6

Oh my zsh.

chmouel

set -ex
v=${1}

[[ -z ${v} ]] && {
    echo "You need a release number i.e: 0.3.1"
}

for p in bash controller creds-init entrypoint git-init kubeconfigwriter nop webhook;do
    docker pull registry.svc.ci.openshift.org/openshift/knative:tektoncd-pipeline-${p}
    docker tag registry.svc.ci.openshift.org/openshift/knative:tektoncd-pipeline-${p} quay.io/openshift-pipeline/tektoncd-pipeline-$p:v${v}

vbatts

walkthrough: buildah on knative

The buildah utility is a versitile container build tool that does not require a daemon (everything is direct invocation). See my "deep dive" for a few hands on use-cases.

Recently knative was announced. It is a project to enable the kubernetes primitives needed to build a functions-as-a-service. There are a plumbing services needed around this use-case, "build" is one of them. Building containers is largely an indepenent goal and story of "serverless" or "FaaS", but I get why they are grouped together.

vbatts

FROM buildpack-deps:stretch-scm

# gcc for cgo
RUN apt-get update && apt-get install -y --no-install-recommends \
		g++ \
		gcc \
		libc6-dev \
		make \
		pkg-config \
	&& rm -rf /var/lib/apt/lists/*

rodricels

# My tmux configuration, partly based on https://github.com/wbkang/wbk-stow/blob/master/tmux-config/.tmux.conf

# Scroll History
set -g history-limit 50000

# show messages for 4 seconds instead
set -g display-time 4000

# set first window to index 1 (not 0) to map more to the keyboard layout
set-option -g renumber-windows on

ericlong

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Hello from Build'
      }
    }
    stage('Test') {
      steps {