Design an OpenRig agent team around a project goal. Create team and agent specifications, role guidance, and collaboration rules, then validate the setup and diagnose problems with startup instructions or agent coordination.
- Designing an implementation and QA pair
- Creating a team with development and independent review
- Writing role guidance and team collaboration rules
mvschwarz/openrig☆ 8.2KUpdated Oct 25, 2026
Open terminal views for OpenRig agents in cmux, grouped by rig, pod, mission, slice, or saved view. Inspect connection health and view agent sessions with read-only access where required, while keeping the underlying sessions running.
- View a rig's agent terminals together in cmux
- Monitor mission or slice terminals in read-only mode
- Reopen a saved terminal view
mvschwarz/openrig☆ 8.2KUpdated Oct 25, 2026
Define reusable OpenRig agent setups, roles, and workflows in specification files. Review dependencies that prevent use on another host, distinguish specifications from bundles and extensions, and verify both file structure and actual execution.
- Defining reusable agent roles and workflows
- Reviewing specifications for use on another host
- Testing specifications in a clean OpenRig environment
mvschwarz/openrig☆ 8.2KUpdated Oct 25, 2026
Guide changes to OpenRig itself by locating relevant source files, choosing tests, assessing sensitive areas, and preparing pull requests. Use isolated test environments to check changes without disrupting the daemon running the current agent session.
- Locate the source files responsible for a behavior
- Choose tests for an OpenRig change
- Test without disrupting the current agent session
mvschwarz/openrig☆ 8.2KUpdated Oct 25, 2026
Guide a development team from an assigned user outcome through implementation, testing, and handoff. It covers reproducing defects, checking behavior against requirements, involving design when needed, and reporting the exact changes, verification results, and remaining uncertainty.
- Start implementation from the assigned user outcome
- Reproduce a defect and verify its repair
- Review delivered behavior against requirements
mvschwarz/openrig☆ 8.2KUpdated Oct 25, 2026
Create reusable starting configurations that combine an agent’s role, startup context, and source history. The skill guides registry entries, checks whether their sources are current, and manages their progression from initial capture to recommendation or retirement.
- Create reusable startup context for an agent role
- Refresh an agent workspace from an existing starter
- Check a starter’s source history and freshness
mvschwarz/openrig☆ 8.2KUpdated Oct 25, 2026
Understand how OpenRig organizes a team of coding agents. This skill explains the main terms, shows how to identify an agent’s role and peers, and clarifies where skills and working context come from.
- Getting oriented in a new OpenRig environment
- Understanding rig, pod, and seat terminology
- Checking where skills and context come from
mvschwarz/openrig☆ 8.2KUpdated Oct 25, 2026
Manage OpenRig development work from setup to completion using shared specification, progress, and evidence files. Record what was actually checked and pass work to the next owner so handoffs and conversation compaction preserve the context.
- Starting a development task with clear completion criteria
- Recording progress and verification evidence
- Handing work to another agent
mvschwarz/openrig☆ 8.2KUpdated Oct 25, 2026
Look up exact syntax, options, JSON output, defaults, and error meanings for a known OpenRig command. Use the reference to check command behavior and diagnose runtime differences against the installed help and running daemon.
- Checking required flags for a known rig command
- Looking up queue commands and handoff syntax
- Investigating command errors and daemon compatibility
mvschwarz/openrig☆ 8.2KUpdated Oct 25, 2026
Design and run bounded procedures in environments where current conditions are uncertain. The skill separates agent judgment from precise tool actions, verifies each effect, and records checkpoints so interrupted work can resume from observed evidence.
- Designing procedures for environments with varying conditions
- Resuming interrupted operations from verified evidence
- Deciding whether an agent or ordinary code should control a procedure
mvschwarz/openrig☆ 8.2KUpdated Oct 25, 2026
Design and maintain applications where OpenRig agents help run the system. Organize instructions, shared state, and artifact checks, then trace unexpected behavior to the code, skill, or schema that needs repair.
- Designing an application operated by OpenRig agents
- Organizing instructions and shared application state
- Tracing unexpected behavior to its source
mvschwarz/openrig☆ 8.2KUpdated Oct 25, 2026
Set up OpenRig to run a team of coding agents, including Claude Code and Codex. Open the team interface, pass project goals to its operator, reconnect to agents, and follow assigned work through to its results.
- Installing OpenRig and starting a coding team
- Returning to an existing team's interface
- Passing project goals to the team operator
mvschwarz/openrig☆ 8.2KUpdated Oct 25, 2026
Review assigned code changes against project conventions, architecture, and intended behavior. Verify findings with source code and tests, classify their severity, and record a merge readiness verdict, with an optional deeper process for independent reviews and resolving disagreements.
- Reviewing assigned code changes
- Checking duplication and inconsistent patterns
- Reviewing fixes that lack a written specification
mvschwarz/openrig☆ 8.2KUpdated Oct 25, 2026
Investigate bugs, failed tests, and unexpected behavior through reproducible steps, evidence gathering, and comparison with working code. Test one hypothesis at a time, then implement a focused fix and verify it with tests.
- Investigating failed tests or builds
- Tracing production bugs across components
- Reassessing a problem after repeated failed fixes
mvschwarz/openrig☆ 8.2KUpdated Oct 25, 2026
Answer Python questions and write code using examples fetched from pythonsheets.com. Find patterns for syntax, asynchronous tasks, networking, databases, machine learning, and distributed computing, or use topic-based questions to prepare for Python interviews.
- Preparing for Python interviews
- Learning asyncio through examples
- Writing a socket server
crazyguitar/pysheeet☆ 8.2KUpdated Oct 24, 2026
Write, review, and refactor Python code using concrete readability rules. Keep functions focused, reduce nested logic, clarify names and expressions, and apply Python features such as comprehensions, dataclasses, and pathlib while respecting existing codebase conventions.
- Refactoring long functions and deeply nested logic
- Reviewing names and complex expressions
- Organizing code with Python standard library features
crazyguitar/pysheeet☆ 8.2KUpdated Oct 24, 2026
Prepare Gentle AI changes for review by linking approved issues, following branch and commit naming rules, and drafting pull requests with observed test results. Check change size and required automated checks before claiming readiness.
- Preparing a branch for a fix or feature
- Drafting a pull request linked to an approved issue
- Organizing test results and reviewer notes
Gentleman-Programming/gentle-ai☆ 8KUpdated Oct 25, 2026
Audit existing SKILL.md files for clear activation conditions, usable instructions, and defined outputs. Get prioritized findings and specific improvements, with changes applied only when requested and the author's intent preserved.
- Audit existing skills for quality issues
- Clarify when a skill should activate
- Move lengthy examples into supporting files
Gentleman-Programming/gentle-ai☆ 8KUpdated Oct 25, 2026
Split large code changes into linked pull requests, each with a focused scope. Organize their order, dependencies, and verification steps so reviewers can assess one unit of work at a time.
- Splitting a pull request with more than 400 changed lines
- Planning the review order for dependent changes
- Integrating a feature through a shared branch
Gentleman-Programming/gentle-ai☆ 8KUpdated Oct 25, 2026
Split changes exceeding 400 lines into linked pull requests with clear boundaries and dependencies. Choose a chain structure, keep tests and documentation with each work unit, and document review order, verification plans, and justified size exceptions.
- Splitting a change that exceeds 400 lines
- Planning PRs that can merge independently
- Coordinating a feature through a draft tracker PR
Gentleman-Programming/gentle-ai☆ 8KUpdated Oct 25, 2026
Prepare and manage GitHub bug reports and feature requests using repository evidence and required forms. Check for duplicates, identify missing information, and verify published issues or comments before reporting the result.
- Preparing a bug report using the required issue form
- Checking for duplicate feature requests
- Adding information to an existing issue
Gentleman-Programming/gentle-ai☆ 8KUpdated Oct 25, 2026
Coordinate temporary agents for code exploration, independent implementation tasks, verification, reviews, or complex debugging. Define self-contained assignments, run independent work in parallel, and check returned evidence before combining the results.
- Delegating codebase exploration to inform a decision
- Running independent implementation tasks in parallel
- Getting an independent check of a high-risk change
Gentleman-Programming/gentle-ai☆ 8KUpdated Oct 25, 2026
Prepare pull requests by checking approved issue links, change-type labels, and required automated checks. Draft the repository’s PR template using observed test results, while leaving commits, pushes, PR creation, and merging under human control.
- Preparing a branch for review
- Drafting a PR linked to an approved issue
- Checking required CI before declaring a PR merge-ready
Gentleman-Programming/gentle-ai☆ 8KUpdated Oct 25, 2026
Turn reusable workflows and project conventions into concise instructions for AI agents. Structure SKILL.md with required metadata, move supporting material into local files, and register project skills in AGENTS.md when applicable.
- Turning a recurring workflow into an agent skill
- Documenting project conventions for AI agents
- Moving lengthy explanations into supporting files
Gentleman-Programming/gentle-ai☆ 8KUpdated Oct 25, 2026