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

Offen
  • Stimmt etwas nicht?
#715 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
1/100
Issue-Typ
Dokumentation
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
tooling

Rechercherichtung

This issue contains an automatically generated file summary, but does not request a change or identify a task. Start by checking the repository's open issues for a follow-up request tied to this summary; done would require a specific change and acceptance criteria.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

ai-agent automation
Global Summary

Rig is a minimal TypeScript agent harness. The core runtime (rig.ts) provides typed schemas, prompt intents, addons, workflows and a Copilot SDK runtime. Pluggable engines (Anthropic, Codex, DeepSeek, Gemini, Pi) share lifecycle helpers. The repo also has launcher/tool utilities, CI drivers and fixtures for provider integration (a three-judges scenario), and integration tests.

Individual File Summaries
File Summary
./.agents/skills/rig/engines/anthropic.ts Anthropic SDK-based engine factory with JSON-schema output and tool support.
./.agents/skills/rig/engines/codex.ts Engine adapter for the OpenAI Codex SDK, using threads and response schemas.
./.agents/skills/rig/engines/deepseek.ts Engine adapter for the DeepSeek harness SDK client.
./.agents/skills/rig/engines/gemini.ts Gemini engine that spawns a CLI subprocess and manages turns.
./.agents/skills/rig/engines/pi.ts Engine adapter for the Pi agent core, converting tools to Pi tool schemas.
./.agents/skills/rig/engines/utils.ts Shared helpers: agent lifecycle (abort and no-concurrent-turn guard), tool schema and result conversion.
./.agents/skills/rig/globals.ts Ambient workflow helpers (call, pipeline, parallel) delegating to the active workflow run.
./.agents/skills/rig/launch-tool.ts Creates a Copilot SDK tool that launches a rig program via the launcher subprocess.
./.agents/skills/rig/rig.ts Core runtime (~3.5k lines): schemas, prompt intents, addons, workflows, Copilot SDK runtime and launcher CLI.
./.agents/skills/rig/run.ts Entry point that runs the installed skill's launcher CLI.
./.github/drivers/codex-fixture-mcp.ts Driver exposing the integration fixture launcher to Codex via an MCP HTTP server.
./.github/drivers/copilot-sdk-driver.ts Copilot SDK driver that runs the rig launch tool in CI.
./.github/drivers/pi-rig-extension.ts Pi extension tool that runs the three-judges fixture and validates output.
./.github/fixtures/assert-three-judges.ts Asserts the three-judges result has the expected engine, model and judgments.
./.github/fixtures/pi-gateway.ts Loads Pi gateway provider configuration for OpenAI-compatible APIs.
./.github/fixtures/provider-fixture.ts Builds provider fixtures across Codex, DeepSeek, Gemini and Pi engines.
./.github/fixtures/provider-three-judges.ts Default export of the provider three-judges fixture.
./.github/fixtures/three-judges.ts Defines three judge agents (clarity, safety, feasibility) in a workflow.
./scripts/haiku.integration.test.ts Integration tests running haiku/sonnet/complex samples against the live Copilot SDK.
./scripts/rig-launch-tool.integration.test.ts Live integration test running the three-judge fixture via a harness-owned launch tool.

Note: summaries are based on file headers and imports; only the first 20 files (sorted) were included.

Generated by Daily Rig File Summarizer · copilot · auto · ~14 AIC · ⌖ ~1 AIC · ⊞ 3.9K · ◷

  • expires on Oct 31, 2026, 2:32 PM UTC
Vorherrschende Sprache
TypeScript
Sterne
14
Forks
0
Ø Merge
9 Std. 27 Min.
Gemergte PRs (30 T.)
34

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.