[rig-summarizer] Daily file summary — 2026-10-17
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 1/5
- Tiempo estimado
- Menos de una hora
- Aptitud para principiantes
- 15/100
- Tipo de issue
- Documentación
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions, typescript
- Área
- documentation
Línea de trabajo
This is an automatically generated daily file summary with no requested change or acceptance criteria. Start by checking the linked workflow run and the summarized files, but there is no defined edit or test that would indicate completion.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Global Summary
Rig is a minimal TypeScript agent harness. The core runtime (rig.ts) provides declarative agents, schemas and prompt intents, with pluggable engines for Anthropic, Codex, DeepSeek, Gemini and Pi, plus a launch tool and workflow globals. The .github folder holds the Copilot SDK driver, the Codex and Pi integration helpers, and the provider fixtures (including the "three judges" fixture). scripts/ holds integration tests.
Individual File Summaries
| File | Summary |
|---|---|
| ./.agents/skills/rig/engines/anthropic.ts | Anthropic engine factory that converts Rig tools and system messages to Anthropic beta API calls with structured output. |
| ./.agents/skills/rig/engines/codex.ts | Codex engine factory that runs agents through the Codex SDK. |
| ./.agents/skills/rig/engines/deepseek.ts | DeepSeek engine factory that runs agents through the DeepSeek harness and checks the run completed. |
| ./.agents/skills/rig/engines/gemini.ts | Gemini engine factory that runs the Gemini CLI and validates its output. |
| ./.agents/skills/rig/engines/pi.ts | Pi engine factory that adapts Rig tools to Pi agent tools and extracts the response text. |
| ./.agents/skills/rig/engines/utils.ts | Shared engine helpers for agent lifecycle, object tool schemas and tool-result text. |
| ./.agents/skills/rig/globals.ts | Defines the global call workflow function, along with pipeline and parallel, bound to the active workflow context. |
| ./.agents/skills/rig/launch-tool.ts | Creates a tool that launches Rig programs from source. |
| ./.agents/skills/rig/rig.ts | Core Rig runtime (~3500 lines): schema types and helpers, agent construction, prompt intents, validation, repair and the engine interfaces. |
| ./.agents/skills/rig/run.ts | Entry point that runs the installed skill. |
| ./.github/drivers/codex-fixture-mcp.ts | Fixture MCP launcher and server used to test Rig launches from Codex. |
| ./.github/drivers/copilot-sdk-driver.ts | Driver that runs a Rig program through the Copilot SDK using required environment variables. |
| ./.github/drivers/pi-rig-extension.ts | Pi extension that registers a Rig tool. |
| ./.github/fixtures/assert-three-judges.ts | Asserts that three-judges output has the expected shape for an engine. |
| ./.github/fixtures/pi-gateway.ts | Helpers for validating and loading Pi gateway configuration. |
| ./.github/fixtures/provider-fixture.ts | Builds a provider fixture from required environment variables. |
| ./.github/fixtures/provider-three-judges.ts | Default export that creates the provider fixture. |
| ./.github/fixtures/three-judges.ts | Three-judge (clarity, safety, feasibility) fixture program that scores a dummy request. |
| ./scripts/haiku.integration.test.ts | Integration test that runs the haiku sample against a real engine. |
| ./scripts/rig-launch-tool.integration.test.ts | Integration test for the Rig launch tool. |
Generated by Daily Rig File Summarizer · copilot · auto · 14.1 AIC · ⌖ 0.506 AIC · ⊞ 7.5K · ◷
- expires on Oct 24, 2026, 2:31 PM UTC
- Lenguaje dominante
- TypeScript
- Estrellas
- 14
- Forks
- 0
- Merge medio
- 3 h 38 min
- PR fusionados (30 d)
- 29
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
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de githubnext/rig
-
ai-agent automation
Dificultad 3/5 1-2 días Aptitud para principiantes 25/100
githubnext/rig#666 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 4/5 3-5 días Aptitud para principiantes 38/100
githubnext/rig#665 ·
Los mantenedores suelen responder en 1 día
-
ai-agent automation
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
githubnext/rig#663 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
githubnext/rig#662 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
githubnext/rig#661 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de githubnext/rig
Issues similares
-
freshness freshness:observed-only
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
thoroc/context-radar#280 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
-
documentation story
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
Billing: computeBundleEconomicsFrom treats a NULL component cost as 0, inflating bundle marginAbiertobug category:billing priority:p3 track:fast
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
LanternOps/breeze#9223 ·
Los mantenedores suelen responder en 1 día