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-17

Ouverte
  • Quelque chose ne va pas ?
#664 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é
1/5
Temps estimé
Moins d'une heure
Accessibilité débutants
15/100
Type d'issue
Documentation
Clarté
À clarifier
Activité
Active
Stack technique
github-actions, typescript
Domaine
documentation

Piste de recherche

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.

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

Description

ai-agent automation
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
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.