repo-setup

Plugin repo-setup from marketplace repo-standards in phanlemanh/repo-standards. Commands read from the repo's manifest — yesterday.

Skills (11)

• ontology-add

  Add or change a business concept in the repo's ontology — entity, property, subtype rule or relation — keeping glossary, entity YAML, relations, wiki page and generated types in sync. Use when the user introduces a new domain concept, changes a business rule, or asks to model their domain.

• review-change

  Independently review a change you did not write — intent and acceptance criteria, tests, domain names, security and personal data, risk tier and records — and give one verdict with findings. Use before opening or merging a pull request, or when asked to review a branch or PR.

• wiki-health

  Health-check the repo's ontology and wiki — structural lint plus a review for contradictions, stale claims versus the code, missing entity pages and superseded decisions — and propose fixes. Use periodically, before a release, or when the user says the wiki or ontology may be outdated or inconsisten

• wiki-ingest

  Update the repo wiki from recent work — a branch/PR diff, merged commits, an incident, meeting notes or decisions from the conversation — following ontology/page-types.yaml. Use after finishing a task or PR, after an incident, or when the user says to record, document or update the wiki.

• wiki-query

  Answer questions about this project's domain, decisions, history or incidents from the repo wiki and ontology, checked against the code, and file valuable answers back into the wiki. Use when the user asks why something is built a certain way, what a business term means, what happened in a past inci

• hello

  Sample skill that greets the user and shows where this plugin's skills live. Replace it with the first real skill. Use when the user asks what this plugin does.

• adopt

  Bring an existing codebase up to the top-tier standard step by step — without breaking it, replacing its tools, or adding sample code — including AGENTS.md/CLAUDE.md, ontology/ and wiki/ seeded from the real code. Use when the user wants to standardise, modernise, clean up or make AI-ready a repo th

• doctor

  Check any repository against the team's top-tier checklist, give a 0-100 score, explain gaps in plain language and fix them safely. Use when the user asks to audit, review, check the health of, or standardise an existing repo.

• explain

  Explain, in plain language, any file, tool or rule that repo-setup added (Makefile, lockfile, pre-commit, gitleaks, CODEOWNERS, ontology, wiki, CI…) and help when a check blocks a commit or a PR. Use when the user asks what something in the repo setup is, why it exists, or why their commit/CI failed

• github

  Connect a repo-setup repository to GitHub — merge settings, staging/production environments, branch ruleset and, when agent workflows are enabled, labels, variables, the Claude GitHub App and secrets — showing every change before applying it. Use after `/repo-setup:new` or `/repo-setup:adopt` at tea

• new

  Set up a new or empty repository through decision layers — context, repo strategy, architecture, AI in the product, stack, domain, design, quality, delivery, agents — with two or three reasoned options at each layer, independent critique and an automated build. Works for newcomers who hand everythin

Similar plugins