Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[rig-summarizer] Daily file summary — 2026-10-12

Abierto
  • ¿Algo no está bien?
#630 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
1/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
typescript
Área
tooling

Línea de trabajo

The issue contains a generated summary of Rig files, but it does not specify a change to make or a result to deliver. Start by reading .agents/skills/rig/rig.ts and the listed engine files to understand the project; the issue provides no completion criteria.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

ai-agent automation
Global Summary

The project is a minimal TypeScript multi-agent harness ("Rig") centered on skills/rig/rig.ts, which provides schema-typed agents, prompt intents, sub-agent delegation, and workflow orchestration atop the Copilot SDK. Pluggable engine adapters (Anthropic, Codex, DeepSeek, Gemini, Pi) in skills/rig/engines/ share lifecycle and tool-schema helpers from utils.ts, letting the same agent API run against different model providers. Supporting infrastructure includes a harness-owned launch tool (launch-tool.ts/run.ts) that runs trusted Rig programs without exposing SDK credentials to arbitrary shell code, GitHub Actions drivers (.github/drivers/) that wire Codex/Pi sessions into the harness's permission and tool systems, and fixture/integration tests (.github/fixtures/, scripts/*.integration.test.ts) that validate a three-judge approval workflow and real single-agent sample runs across providers.

Individual File Summaries
File Summary
.agents/skills/rig/engines/anthropic.ts Implements anthropicEngine, an AgentFactory wrapping the Anthropic SDK's beta tool runner with structured JSON output support and tool/text message handling.
.agents/skills/rig/engines/codex.ts Implements codexEngine, wrapping @openai/codex-sdk threads to run prompts with optional structured output schemas; does not support Rig tools.
.agents/skills/rig/engines/deepseek.ts Implements deepseekEngine using the DeepSeek Harness SDK session API, handling cancellation, cleanup, and completed-turn validation.
.agents/skills/rig/engines/gemini.ts Implements geminiEngine, spawning the Gemini CLI as a subprocess per turn with session resumption and JSON output parsing.
.agents/skills/rig/engines/pi.ts Implements piEngine, wrapping @earendil-works/pi-agent-core to run prompts and tools against a configurable Pi model registry.
.agents/skills/rig/engines/utils.ts Shared engine utilities: a agentLifecycle helper enforcing single-turn concurrency with abort support, plus tool schema/result-text conversion helpers.
.agents/skills/rig/globals.ts Exposes ambient call, pipeline, and parallel helpers that delegate to the active WorkflowContext, simplifying workflow-style agent invocation.
.agents/skills/rig/launch-tool.ts Defines createRigLaunchTool, a Copilot SDK tool that spawns an isolated Rig launcher subprocess to run trusted TypeScript source without exposing connection credentials to it.
.agents/skills/rig/rig.ts The core Rig runtime: declarative schema helpers, prompt intents, agent/workflow construction, Copilot SDK engine, and the launcher CLI entry point.
.agents/skills/rig/run.ts Thin entry point that imports and runs runLauncherCli from rig.ts when executed as the main module.
.github/drivers/codex-fixture-mcp.ts Implements a Docker/chroot-isolated Codex fixture launcher and a minimal JSON-RPC MCP server exposing a single run_rig tool for the three-judge integration test.
.github/drivers/copilot-sdk-driver.ts A GitHub Actions driver that creates a Copilot SDK session, registers the harness-owned Rig launch tool, and enforces single-use execution of a prevalidated fixture.
.github/drivers/pi-rig-extension.ts Registers a run_rig Pi agent tool that launches the checked-in three-judge fixture exactly once and validates/writes its JSON result.
.github/fixtures/assert-three-judges.ts Provides assertThreeJudges, validating the shape and verdict of a three-criterion (clarity/safety/feasibility) judgment result, plus a CLI entry point for ad hoc checks.
.github/fixtures/pi-gateway.ts Builds a Pi model registry from a harness-provisioned "aw-gateway" provider configuration, validating its shape and exposing the selected model.
.github/fixtures/provider-fixture.ts Selects and configures a provider engine (Codex, Gemini, DeepSeek, or Pi) based on RIG_JUDGE_ENGINE, returning a configured three-judge workflow.
.github/fixtures/provider-three-judges.ts Minimal entry point that default-exports the workflow created by createProviderFixture().
.github/fixtures/three-judges.ts Defines the reusable three-judge workflow (clarity/safety/feasibility) used to sanity-check provider engine integrations with a dummy request.
scripts/haiku.integration.test.ts Integration tests that spawn the Rig launcher against real haiku/sonnet/complex samples using live Copilot SDK credentials when available.
scripts/rig-launch-tool.integration.test.ts An opt-in live integration test verifying the harness-owned run_rig launch tool runs the three-judge fixture once without exposing connection credentials.

Generated by Daily Rig File Summarizer · copilot · auto · 94.7 AIC · ⌖ 6.22 AIC · ⊞ 7.5K · ◷

  • expires on Oct 19, 2026, 2:51 PM UTC
Lenguaje dominante
TypeScript
Estrellas
13
Forks
0
Merge medio
3 h 44 min
PR fusionados (30 d)
28

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/rig

Todos los issues de githubnext/rig

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.