Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

welcomer

Étoiles4

Forks5

Mis à jour9 juin 2026 à 21:23

Greet a user starting a new project and walk them through a minimal onboarding checklist. Use when the user opens a fresh repo, says "let's start", "новий проєкт", "kickoff", or asks how to begin. Use even if the user does not mention onboarding or welcome by name.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

genkovich

genkovich/agentic-engineering-course-public

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

SKILL.md

readonly

name	welcomer
description	Greet a user starting a new project and walk them through a minimal onboarding checklist. Use when the user opens a fresh repo, says "let's start", "новий проєкт", "kickoff", or asks how to begin. Use even if the user does not mention onboarding or welcome by name.
allowed-tools	Read, Bash

Welcomer

Універсальний onboarding skill для демонстрації як plugin skills працюють.

Workflow

Прочитай README.md у поточній директорії якщо існує — отримай контекст проєкту
Виконай git log -1 --format="%h %s" щоб зрозуміти останній стан репо
Запропонуй користувачу 3 наступні кроки на основі контексту:
- Що варто прочитати першим
- Яка команда дасть швидкий результат
- На що звернути увагу в архітектурі
Заверши коротким підсумком у дві-три фрази

Тон

Дружній, прямий, без зайвих формальностей. Українською якщо користувач писав українською, англійською — інакше.

Plus depuis ce dépôt

même dépôt

prepare-vps-deploy

genkovich/agentic-engineering-course-public

Prepare and verify the repository files required to deploy this Next.js project to one Ubuntu VPS with Docker Compose and a GitHub self-hosted runner. Use when creating or reviewing Dockerfile.production, compose.vps.yml, the health route, persistent SQLite storage, or deploy-vps.yml before a VPS release.

2026-07-154

bump-version

genkovich/agentic-engineering-course-public

Decide and apply the next semver for a release. Triggers on "bump the version", "what version is next", "/bump-version", "простав версію", "яка наступна версія". Reads the next number from the deterministic scripts/next-version.sh (NEVER guesses it), explains in plain language WHICH part moved and why (e.g. "MINOR, because a feat landed: filter notes by tag"), edits the version line in pyproject.toml, and proposes the matching `git tag vX.Y.Z`. The number is decided by a rule; the agent explains and applies — the human confirms the tag. Never pushes a tag itself.

2026-07-064

check-docs-drift

genkovich/agentic-engineering-course-public

Find and fix where docs/api.md fell behind the code. Triggers on "check for doc drift", "is the API doc up to date", "/check-docs-drift", "перевір дрейф документації", "docs drift". Runs the deterministic scripts/check-docs-drift.py (parses the public NoteBook methods with ast, compares to what docs/api.md documents — NO LLM finds the gap), reports the drift, and PROPOSES the doc edit that closes it. The gap is found by parsing; the agent writes the missing documentation in the doc's existing style. Edits only docs/; never commits or pushes.

2026-07-064

codify-rule

genkovich/agentic-engineering-course-public

Turn a repeated mistake into a durable, path-scoped rule in .claude/rules/. Triggers on "codify this rule", "make a rule so this doesn't happen again", "/codify-rule", "закодифікуй правило", "петля помилка-правило". Use only when the same mistake showed up TWICE (twice = a pattern, once = noise). Names the wrong shape and the right shape with one short example of each, scopes the rule to the paths that matter, and leaves the edit in the working tree so the next agent on this repo inherits the fix. Edits only .claude/rules/; never commits or pushes.

2026-07-064

curate-changelog

genkovich/agentic-engineering-course-public

Curate the [Unreleased] section of docs/CHANGELOG.md from git history. Triggers on "curate the changelog", "update the changelog", "/curate-changelog", "онови changelog", "курування журналу". Reads git log since the last tag, FILTERS out what a reader never feels (test/ci/chore/merge), GROUPS commits about one feature into one bullet, and REWRITES technical subjects into plain language under the six Keep a Changelog categories (Added/Changed/Deprecated/ Removed/Fixed/Security). The result must have FEWER lines than the raw log — that is the proof of curation, not a dump. Leaves the edit in the working tree; never commits or pushes.

2026-07-064

release-notes

genkovich/agentic-engineering-course-public

Draft partner-facing release notes from the same commits as the changelog. Triggers on "draft release notes", "release notes for the next version", "/release-notes", "нотатки релізу", "release notes партнеру". Same input as curate-changelog, different audience and tone: a short, benefit-first narrative for a user or partner — "what's new for you" — not a categorized engineer's list. Keeps only changes a user actually notices; drops internal refactors and tooling. Prints the notes to the chat to seed a GitHub Release description or a partner announcement. Writes no file.

2026-07-064

name	welcomer
description	Greet a user starting a new project and walk them through a minimal onboarding checklist. Use when the user opens a fresh repo, says "let's start", "новий проєкт", "kickoff", or asks how to begin. Use even if the user does not mention onboarding or welcome by name.
allowed-tools	Read, Bash

Welcomer

Універсальний onboarding skill для демонстрації як plugin skills працюють.

Workflow

Прочитай README.md у поточній директорії якщо існує — отримай контекст проєкту
Виконай git log -1 --format="%h %s" щоб зрозуміти останній стан репо
Запропонуй користувачу 3 наступні кроки на основі контексту:
- Що варто прочитати першим
- Яка команда дасть швидкий результат
- На що звернути увагу в архітектурі
Заверши коротким підсумком у дві-три фрази