add-dict

Manages project dictionary terms by deduplicating and adding reusable vocabulary during PR workflows.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill add-dict-ryokuman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-dict
Source: https://github.com/Ryokuman/new_human_ochestrator/tree/main/system/20-skills/add-dict
Command: npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill add-dict-ryokuman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams accumulate inconsistent terminology across PRs, tasks, and reports, causing reviewers to struggle with undefined abbreviations and duplicate expressions for the same concept. This Skill standardizes how new terms are checked against an existing project dictionary before anything is added. ## Core Features & Use Cases - Duplicate-first terminology review: Extracts candidate terms from PR bodies, task descriptions, review comments, and logs, then checks the existing project dictionary for equivalent or similar expressions before adding anything new. - Structured dictionary entries: Records each term with change type, definition, usage context, examples, source, and dictionary file location in the project SSoT layer. - PR body integration: Updates the PR's noun explanation and newly added words sections, and flags common-rule promotion candidates separately without applying them to the root system layer. - Use Case: While writing a PR that repeatedly uses an internal runner abbreviation, the Skill checks the project dictionary, finds no equivalent term, and adds a properly defined entry while updating the PR body accordingly. ## Quick Start Ask the agent to review the terms used in this PR and add any genuinely new reusable vocabulary to the project dictionary.

Frequently Asked Questions about add-dict

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add new terminology to a project dictionary?

Extract candidate terms from PR bodies, task descriptions, and review comments, then search the existing project dictionary for equivalent or similar expressions first. Only add terms that are genuinely new and reusable, recording definition, usage context, example, and source.

When should a term not be added to a project dictionary?

Skip adding a term when an existing dictionary entry covers the same concept, when the expression is a one-off phrase used only in a single PR, or when it is understandable as plain language without project context. Weakly sourced or sensitive expressions should also be excluded.

Where are project dictionary terms stored?

Project-internal terms are stored in the project SSoT layer, typically at projects/<project-id>/02-project-internal/10-dictionary/project-dictionary.md. Project-specific raw terms are never copied into the root system layer without separate approval.

How does dictionary management integrate with PR reviews?

During PR authoring or review, repeated or undefined terms trigger a dictionary check. The PR body is updated with a noun explanation section and a newly added words table, or marked as not applicable when no dictionary changes occurred.

Can common terms be promoted to shared system rules?

Terms recurring across multiple projects can be flagged as common-rule candidates in feedback or follow-up sections. They are not applied to the root system layer without explicit user approval.