Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#638 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-3 heures
Accessibilité débutants
8/100
Type d'issue
Documentation
Clarté
À clarifier
Activité
Active
Stack technique
github-actions, typescript
Domaine
ai-infra-agents, devtools

Piste de recherche

This is an automated daily file summary with no requested change, so there is nothing to implement. Start by checking whether any listed file, such as .agents/skills/rig/rig.ts or .github/fixtures/assert-three-judges.ts, has a summary that is wrong or stale. Done would mean a maintainer confirms the summary needs a specific correction, which should be asked for in the thread first.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

ai-agent automation
Global Summary

This project (Rig) is a minimal TypeScript multi-agent harness centered on skills/rig/rig.ts, which defines schemas, prompt intents, agent/workflow abstractions, and a Copilot SDK runtime. Additional pluggable engines (Anthropic, Codex, DeepSeek, Gemini, Pi) adapt third-party AI SDKs or CLIs to Rig's AgentFactory interface, sharing lifecycle/tool-schema utilities. The .github directory contains CI fixtures and drivers that exercise a 'three-judges' evaluation workflow across these engines inside sandboxed/dockerized environments, with assertion helpers validating judgment output. Sample and test files (.tmp-agent, scripts) demonstrate real usage patterns, such as a file-summarization multi-agent pipeline and integration tests spawning the launcher CLI against sample agent programs.

Individual File Summaries
File Summary
./.agents/skills/rig/engines/anthropic.ts Implements an AgentFactory wrapping the Anthropic SDK beta client, converting Rig tools to Anthropic tool schemas and managing ask/close lifecycle with a single-turn guard.
./.agents/skills/rig/engines/codex.ts Implements an AgentFactory around the OpenAI Codex SDK thread API; does not support Rig tools and configures developer instructions from the system message.
./.agents/skills/rig/engines/deepseek.ts Implements an AgentFactory using the DeepSeek harness SDK session API, without Rig tool support, handling session close and turn lifecycle.
./.agents/skills/rig/engines/gemini.ts Implements an AgentFactory that shells out to the Gemini CLI via child_process, parsing JSON stdout responses and tracking a session id across turns.
./.agents/skills/rig/engines/pi.ts Implements an AgentFactory bridging to the pi-agent-core/pi-ai SDKs, resolving models by provider and converting Rig tools to Pi tool definitions.
./.agents/skills/rig/engines/utils.ts Shared engine helpers: agentLifecycle manages single-turn concurrency/abort semantics, plus objectToolSchema and toolResultText utilities for tool schema/result handling.
./.agents/skills/rig/globals.ts Ambient workflow context helpers (call, pipeline, parallel) that delegate to the currentWorkflow() context, easing porting of Claude-style dynamic workflows.
./.agents/skills/rig/launch-tool.ts Creates a 'run_rig' Copilot SDK tool that spawns a trusted Rig TypeScript program as a subprocess, scrubbing connection credentials from its environment.
./.agents/skills/rig/rig.ts Core Rig runtime (~3500 lines): defines Json/Schema types, AgentSpec/AgentFn, prompt intents, workflow orchestration (call/pipeline/parallel), and the Copilot SDK-based engine and launcher CLI.
./.agents/skills/rig/run.ts Thin CLI entrypoint that imports and invokes runLauncherCli from rig.ts when executed directly.
./.github/drivers/codex-fixture-mcp.ts Builds a one-shot fixture launcher that spawns a sandboxed Codex process via docker/chroot and validates output against the three-judges assertion helper.
./.github/drivers/copilot-sdk-driver.ts Driver script that loads action helper modules, parses multi-provider/tool config from environment, extracts a Rig fixture source from a prompt file, and runs it against the Copilot SDK.
./.github/drivers/pi-rig-extension.ts Creates a one-shot Pi agent tool ('run_rig') that executes the checked-in Pi three-judge Rig fixture and validates its output.
./.github/fixtures/assert-three-judges.ts Test assertion helper validating the shape and content of three-judge workflow results (engine, model, judgments, verdict) per engine.
./.github/fixtures/pi-gateway.ts Validates and extracts a harness-provisioned Pi 'aw-gateway' provider configuration (baseUrl, api, model, limits) from an arbitrary JSON value.
./.github/fixtures/provider-fixture.ts Selects and configures a provider engine (codex, gemini, deepseek, etc.) from environment variables to build the three-judges workflow for integration testing.
./.github/fixtures/provider-three-judges.ts Tiny entrypoint exporting the default workflow instance produced by createProviderFixture().
./.github/fixtures/three-judges.ts Defines the three-judge dummy-request workflow: a judge agent evaluating clarity/safety/feasibility criteria orchestrated via Rig's workflow/call API.
./scripts/haiku.integration.test.ts Vitest integration test that spawns the Rig launcher against haiku/sonnet sample programs over stdio or SDK-URI transport, skipped unless Copilot credentials are present.

Generated by Daily Rig File Summarizer · copilot · auto · 70.5 AIC · ⌖ 7.07 AIC · ⊞ 7.5K · ◷

  • expires on Oct 20, 2026, 2:45 PM UTC
Langage dominant
TypeScript
Étoiles
14
Forks
0
Merge moyen
3 h 38 min
PR mergées (30 j)
29

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de githubnext/rig

Toutes les issues de githubnext/rig

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.