Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Make required skills and tool integrations usable in native channels

Abierto
  • ¿Algo no está bien?
#56 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
developer-experience, tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
1
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/ace2

Todos los issues de githubnext/ace2

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.