Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Make required skills and tool integrations usable in native channels

Aperta
  • Qualcosa non va?
#56 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
developer-experience, tooling

Direzione di ricerca

Start with the linked review evidence in issue #5 (comment 5986485157) and the referenced issues #27 (composer selection) and #9 (external-harness hosting) to understand current instruction/skill discovery. Then locate the native-channel loading path for root AGENTS/CLAUDE instructions and skill discovery, and build the inventory called for in the first acceptance bullet (lane/review workflows, React Doctor, docs research). Done means a real selected skill and a cited primary-document workflow run end-to-end with results retained in Ace, and unavailable capabilities surfaced explicitly rather than silently dropped.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Native channels load root AGENTS/CLAUDE instructions and list repository skills (.agents/skills, .claude/skills) and rules (.claude/rules) in the prompt (packages/channel/src/context.ts, d5fc23c). Ace bundles the lane CLI and puts it first on agents' PATH (#233), so this repository's lane skill works through the shell tool. Still missing: user-level/plugin skills, linked resources resolved per lane, custom-agent execution, and tools a skill requires. Composer selection (#27) and external-harness hosting (#9) were closed as not planned, so this issue no longer depends on them.

Acceptance

  • Inventory the concrete skills and integrations used for Ace work, including lane/review workflows, React Doctor, and documentation research.
  • Resolve the intended instructions and linked resources relative to the correct lane/source, and invoke their required commands/tools.
  • Make unavailable capabilities explicit instead of advertising an unusable skill or silently changing its behavior.
  • Support the selected custom-agent and instruction-discovery semantics, with source/precedence visible and preserved across continuation.
  • Demonstrate a real selected skill and a cited primary-document research workflow, with results retained in Ace.

A supported shell route can satisfy a workflow. Do not turn this into blanket compatibility with every installed plugin or MCP server. Browser tooling has its own issue; #26 owns non-image input.

Related: #9 and #27 (both closed, not planned). This is broader integration work, not a blanket dogfooding MVP gate. Review evidence.

Lingua principale
TypeScript
Stelle
1
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di githubnext/ace2

Tutte le issue di githubnext/ace2

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.