Split the nine skills into four plugins

Aperta
  • Qualcosa non va?
#9 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github
Ambito
tooling

Direzione di ricerca

Start with the current skills/ layout, README.md, and CONTEXT.md, then check the Claude Code and Codex plugin manifest requirements and test npx skills add against a copy of the proposed layout. Decide where git_cleanup_adviser belongs and name the context plugin, then move skills, add manifests and marketplace files, and update links. Done means all four plugins install with only their own skills and the README commands work on a clean machine.

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

Descrizione

enhancement

Problem

The repository holds nine skills. A plugin is the unit that a person installs, and one plugin can hold one skill or many skills. If all nine skills go into one plugin, a person who wants only the issue skills must also install the personal coding styles of Jérôme Étienne. The skills must be split into several plugins, each with one purpose.

This issue replaces the plan "one plugin at the repository root" in the issue below.

Decision: four plugins

Plugin Skills Purpose
context-md (name to decide) context_md_system Keep the CONTEXT.md files of a repository correct, so that the software stays consistent. This is not documentation.
docs-folder docs_folder_system, docs_folder_agents_rules_system Organize the documentation folder that the coding agents write and read, with the agent rules.
jerome-style jerome-typescript-javascript-style, jerome-rust-style The personal coding styles of Jérôme Étienne. Other people can install them if they want the same styles.
issue-workflow issue_creation, issue_fix_workflow, bug_triage_workflow Create, triage, and fix issues.

Why these groups:

  • The two skills in docs-folder need each other: each one names the other in its SKILL.md.
  • The skill jerome-rust-style names jerome-typescript-javascript-style in its adaptation review, so both stay in jerome-style.
  • No skill in one of the four plugins needs a skill from another plugin.

Plugin names are proposals. Codex uses kebab-case names. The installed skills get the plugin name as a prefix, for example /issue-workflow:issue_creation, so the plugin name appears in every command.

Open decisions

  • The skill git_cleanup_adviser has no plugin. It is not about issues. The skill issue_fix_workflow works in a temporary worktree, and git_cleanup_adviser advises on worktrees, but this is not a reason to join them. Choose: put it in issue-workflow, give it a fifth plugin, or leave it as a skill without a plugin.
  • The final name of the plugin that holds context_md_system.

Folder layout

Four plugins cannot all be the repository root. Each plugin gets its own folder, and the two marketplace files list the four folders:

.claude-plugin/marketplace.json
.agents/plugins/marketplace.json
plugins/<plugin name>/.claude-plugin/plugin.json
plugins/<plugin name>/.codex-plugin/plugin.json
plugins/<plugin name>/skills/<skill name>/SKILL.md

This is the layout that both tools document: the entry source is ./plugins/<plugin name> in the Claude Code file, and the source.path is ./plugins/<plugin name> in the Codex file. It also removes the open question of issue 8 about a Codex plugin at the repository root. Sources: https://code.claude.com/docs/en/plugin-marketplaces.md and https://developers.openai.com/codex/plugins/build/

Risk to prove first

README.md installs skills with the command npx skills add jeromeetienne/coding_agent_plugin, and the skills are in the folder skills/ today. Moving every skill into plugins/<plugin name>/skills/ can break this command. Before the move, run the command on a test copy with the new layout and read the list. If the command does not find the skills, decide whether to keep the old command through a second copy or a link, or to drop it in favor of the plugin commands.

Tasks

  • Decide the open decisions above.
  • Move the skill folders into the plugin folders with git mv.
  • Add the plugin manifest of each of the four plugins for Claude Code and for Codex, and the two marketplace files.
  • Run claude plugin validate . on the repository and on each plugin folder.
  • Install each plugin in Claude Code from the local folder and check with claude plugin details <plugin name> that its skills are listed.
  • Install each plugin in Codex from the local folder and check that its skills load.
  • Run npx skills add on the new layout and read the list of skills that it finds.
  • Update README.md: the table of skills, the install commands, and the links to skills/... paths.
  • Update CONTEXT.md: the rule "The repository has no plugin manifest", and the entry for skills/. Add a CONTEXT.md file in each new folder that holds source.

Acceptance

  • Each of the four plugins installs alone in Claude Code and in Codex, and it installs only its own skills.
  • The commands in README.md work on a clean machine.
  • No link in the repository points to a path that no longer exists.
Lingua principale
Nessun dato sulla lingua
Stelle
1
Fork
0
Merge medio
10m
PR unite (30g)
11

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 jeromeetienne/coding_agent_plugin

Tutte le issue di jeromeetienne/coding_agent_plugin

Issue simili

Altre issue su DevTools

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.