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

[External Plugin]: agent-signage

Cerrado
#3,306 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
62/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
git
Área
devtools, tooling

Línea de trabajo

Review commit 7cf8c0b440eff548c8d378313981475e5e89e902 at the claude-plugin path, starting with claude-plugin/plugin.json and claude-plugin/hooks/hooks.json. Run the spec-compliance and install-smoke checks, plus vally lint, and compare the portable manifest with the Claude Code manifest. Done means the pinned plugin passes review and can be accepted for listing without claiming unsupported portable capabilities.

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

Descripción

external-plugin needs-review:HIGH ready-for-review
Plugin name

agent-signage

Short description

A PreToolUse hook that reports actionable git-state facts before file operations.

GitHub repository

hermes-labs-ai/agent-signage

Plugin path inside the repository

claude-plugin

Ref to review

No response

Commit SHA to review

7cf8c0b440eff548c8d378313981475e5e89e902

Version

0.2.1

License identifier

Apache-2.0

Author name

Rolando Bosch

Author URL

https://github.com/hermes-labs-ai

Homepage URL

https://github.com/hermes-labs-ai/agent-signage

Keywords

git, stale-branch, hooks, pretooluse, agent-reliability, developer-tools

Additional notes for reviewers

Updated to pin a newer immutable commit. The previously pinned SHA 74e7eb623d4e6b0d5fb16163cbfa8d2ec936356b had no Agent Plugins v1 manifest at the submitted plugin root and therefore failed the spec-compliance, install-smoke-test, and version-match gates with "No plugin.json found in a recognized location". PR hermes-labs-ai/agent-signage#17 added claude-plugin/plugin.json and merged to main as 7cf8c0b440eff548c8d378313981475e5e89e902. That merge commit is now pinned above for immutable review; the plugin remains version 0.2.1.

The manifest declares $schema https://agent-plugins.org/schemas/1.0.0/plugin.schema.json and uses only fields allowed by that closed schema. The repository also keeps a separate Claude Code manifest at claude-plugin/.claude-plugin/plugin.json; the two agree on every shared field, and the Claude-only displayName is deliberately absent from the portable manifest.

Scope note, stated plainly: this plugin's portable Agent Plugins surface is manifest metadata only. It ships no skills/ and no mcp.json, so vally lint correctly reports zero skills. Its actual behavior is a Claude Code PreToolUse hook wired through claude-plugin/hooks/hooks.json, which is a client-specific component, not a portable v1 one. No portable capability is claimed that the package does not ship.

No ref is supplied because no release tag points at this commit, so the sha alone is the immutable reference. The plugin is also listed in the independent Hermes Labs marketplace manifest (https://github.com/hermes-labs-ai/copilot-plugins/blob/main/.claude-plugin/marketplace.json) as a git-subdir source at path claude-plugin; that listing is independent of Awesome Copilot external-plugin intake and does not indicate Awesome Copilot acceptance. Submitted by the plugin's own maintainer (Hermes Labs).

Submission checklist
  • The plugin lives in a public GitHub repository.
  • The ref and/or sha I provided is immutable (release tag and/or full 40-character commit SHA), not a branch.
  • This submission follows this repository's contribution, security, and responsible AI policies.
  • This plugin is not already listed in the Awesome Copilot marketplace.
Lenguaje dominante
JavaScript
Estrellas
39.2k
Forks
5k
Merge medio
1 d 18 h
PR fusionados (30 d)
114

Guía de contribución

Abrir la 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 github/awesome-copilot

Todos los issues de github/awesome-copilot

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.