Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
#654 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
1/5
Geschätzter Aufwand
Unter einer Stunde
Anfängerfreundlichkeit
8/100
Issue-Typ
Dokumentation
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
ai

Rechercherichtung

This is an automated daily status report with no requested change, so there is nothing to implement. If you want to check a summarized file, start with ./.agents/skills/rig/rig.ts or the engine files under ./.agents/skills/rig/engines/. Work only if a maintainer later opens a concrete request.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

ai-agent automation
Global Summary

This project is Rig, a minimal TypeScript agent harness. The core runtime (rig.ts) provides declarative agents, and pluggable engines connect it to Anthropic, Codex, DeepSeek, Gemini, Pi and the Copilot SDK. Supporting code includes a launch tool, a skill runner, Copilot/Codex/Pi test drivers, a "three judges" provider fixture, and integration tests.

Individual File Summaries
File Summary
./.agents/skills/rig/engines/anthropic.ts Implements anthropicEngine, an AgentFactory backed by the Anthropic SDK with JSON-schema output and tool-calling support.
./.agents/skills/rig/engines/codex.ts Implements codexEngine, an AgentFactory using the OpenAI Codex SDK with normalized response schemas.
./.agents/skills/rig/engines/deepseek.ts Implements deepseekEngine, an AgentFactory using the DeepSeek harness SDK client.
./.agents/skills/rig/engines/gemini.ts Implements geminiEngine, an AgentFactory that spawns the Gemini CLI as a subprocess.
./.agents/skills/rig/engines/pi.ts Implements piEngine, an AgentFactory built on the Pi agent core, with tool and model support.
./.agents/skills/rig/engines/utils.ts Shared engine helpers: agent lifecycle management, tool schema conversion and tool-result text formatting.
./.agents/skills/rig/globals.ts Declares and exposes Rig's global types and helpers for programs.
./.agents/skills/rig/launch-tool.ts Creates a Copilot SDK tool (createRigLaunchTool) that launches Rig programs as a child process.
./.agents/skills/rig/rig.ts The ~3500-line core runtime with agent construction, schemas (s), prompt intents (p), repair and the Copilot engine.
./.agents/skills/rig/run.ts Small entry point that runs the installed Rig skill.
./.github/drivers/codex-fixture-mcp.ts MCP/HTTP driver that launches the three-judges fixture for Codex and checks the result.
./.github/drivers/copilot-sdk-driver.ts Driver that runs the Rig launch tool through the Copilot SDK and records outputs.
./.github/drivers/pi-rig-extension.ts Defines a Pi tool that runs the Rig fixture and asserts the three-judges result.
./.github/fixtures/assert-three-judges.ts Validates that a three-judges result has the expected criteria and judgment structure.
./.github/fixtures/pi-gateway.ts Builds Pi model providers from a gateway config using OpenAI completions/responses APIs.
./.github/fixtures/provider-fixture.ts Creates a provider fixture that wires the Codex, DeepSeek, Gemini and Pi engines into three-judges.
./.github/fixtures/provider-three-judges.ts Default-exports the provider fixture.
./.github/fixtures/three-judges.ts Defines the three-judges workflow, judging clarity, safety and feasibility of a request.
./scripts/haiku.integration.test.ts Integration test running a haiku Rig program through the launcher, skipped without a Copilot token or SDK URI.
./scripts/rig-launch-tool.integration.test.ts Integration test for the Rig launch tool.

Generated by Daily Rig File Summarizer · copilot · auto · 14.7 AIC · ⌖ 0.505 AIC · ⊞ 7.5K · ◷

  • expires on Oct 22, 2026, 2:36 PM UTC
Vorherrschende Sprache
TypeScript
Sterne
14
Forks
0
Ø Merge
3 Std. 38 Min.
Gemergte PRs (30 T.)
29

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus githubnext/rig

Alle Issues in githubnext/rig

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.