fedoroff-vlad

@fedoroff-vlad source repo

14 skills
0 followers
13 hours ago last updated

▌
Close Pr · fedoroff-vlad
Use when finishing a PR — before or right after merge. Fires on: "close the PR", "wrap up this PR", "PR is green", "move this to history". Moves finished work out of the live status file into the archive, runs a docs freshness pass, and squash-merges once CI is green.

0 installs
▌
Bump Deps · fedoroff-vlad
Use when raising the version of an INCOMING dependency. Fires on: "bump the dependency", "update the library", "upgrade <lib>", "refresh the lockfile", "dependencies are outdated". Bumps the version in the single source of truth, syncs the lockfile, rebuilds, revalidates, and fixes any pinned references.

0 installs
▌
New Skill · fedoroff-vlad
Use when you are about to author a NEW reusable skill in this repo, or rewrite an existing skill's frontmatter so it triggers reliably. Fires on: "create a skill", "add a skill", "why doesn't my skill fire", "write a SKILL.md", "make this skill discoverable". Produces a correctly-shaped SKILL.md with a trigger-style description and updates the skills index.

0 installs
▌
Run Guide · fedoroff-vlad bundle
Use to get an unfamiliar project actually building and running, and to capture the working route as a staged RUN.md. Drives an iterate-until-green loop: attempt → read the failure → fix (toolchain, certs, .env creds, port-forwards) → record → retry. Fires on: "собери и запусти проект", "почему не собирается / не запускается", "нужна инструкция по запуску", "какие сервисы и порты прокинуть через kubectl", "что положить в .env", "make it build/run", "write RUN.md". Asks the user for secrets it cannot derive; never invents them.

0 installs
▌
New Golden · fedoroff-vlad
Use when deciding what to cover with a unit test vs a golden test, when writing a NEW golden test or fixture, or after a bug escaped to production/a real repo and you are asking why the tests missed it. Fires on: "write a golden test", "нужен golden на это", "add a fixture", "what should this test assert", "почему тесты это не поймали", "unit or golden?". Produces the split, a fixture that can actually fail, and structure-not-text assertions. To *run* existing goldens, use `run-goldens` instead.

0 installs
▌
New Module · fedoroff-vlad
Use when creating a new module from the project's canonical layout — a new service, MCP module, agent, or migration. Fires on: "add a new module", "scaffold a service", "new MCP module", "new agent", "new migration". Copies the canonical layout, wires it in, and runs check-drift so no coupled artifact is forgotten.

0 installs
▌
Check Drift · fedoroff-vlad
Use after ANY change and before opening a PR to verify every coupled artifact moved together. Fires on: changed an env var / port / endpoint / MCP tool / dependency / LLM model / DB schema; "did I update everything"; "check drift"; "reconcile the docs". Reads the repo's .skills/change-map.yaml and reports which coupled files did NOT move.

0 installs
▌
Map Project · fedoroff-vlad bundle
Use at the START of onboarding or documenting an unfamiliar project — to scan and index it before writing a line of docs. Fires on: "просканируй проект", "проиндексируй репозиторий", "разберись в проекте X", "map the project", "scan the repo", "что это за проект и из чего он состоит". Runs a mechanical scanner, then reads the flagged files to produce a durable project map: modules, build system, toolchain, deploy manifests, services/ports, env keys, entry points — written to docs/onboarding/project-map.md.

0 installs
▌
Run Goldens · fedoroff-vlad
Use when you want to run the golden LLM tests against a real model — one, a few, or all. Fires on: "прогони голдены" / "run the goldens", "прогони golden тесты", "проверь роутинг/синтез на реальной модели", "did my prompt/skill/router change break the goldens", after editing a prompt, SKILL.md, classifier, or any LLM surface. Discovers the repo's golden tests, lets you pick a scope, runs them through the repo's golden runner, and reads the result (real regression vs flaky borderline case).

0 installs
▌
Scrub Identity · fedoroff-vlad
Use when a repository artifact is about to record WHOSE data a tool was run against — an employer's or client's repo name, package path, hostname, ticket key, or domain vocabulary — in docs, commit messages, PR bodies, tests or fixtures. Fires on: "we proved it on <real repo>", "обезличь", "убери упоминания", "anonymize this", "is this safe to commit", "can this be public", writing a fixture modelled on real data, or a status/architecture note about a production run. Produces the de-identified wording plus a local terms check so the name cannot come back.

0 installs
▌
Release Version · fedoroff-vlad
Use when cutting a stable/production release of THIS project. Fires on: "cut a release", "bump the version", "tag a release", "ship to prod", "release notes". Determines the semver bump from merged PRs, updates version files, generates a changelog, and tags. Distinct from bump-deps (incoming deps vs outgoing version).

0 installs
▌
Document Project · fedoroff-vlad bundle
Use after the project is mapped, to write the human- and agent-facing docs: a per-module README, a root README with the module map, and an AGENTS.md spec skeleton so an agent can develop against it. Fires on: "сделай ридми по проекту", "напиши README по каждому модулю", "задокументируй проект", "нужна документация для онбординга", "write the READMEs", "document each module". Reads docs/onboarding/project-map.md; writes README.md per module + at the root, and a spec skeleton.

0 installs
▌
Add Observability · fedoroff-vlad
Use when adding logging/observability to a new or existing service, module, or pipeline — or when a long-running job turned out to be unexplainable after the fact. Fires on: "add logging", "нужно логирование", "what do we log here", "structured logs", "ship logs to Kibana/Elasticsearch/Loki", "why did this run fail and we can't tell", "add metrics/tracing to this pass". Produces a logging design (event vocabulary, sink, levels, payload rule) written into the architecture doc first, then the wiring.

0 installs
▌
Architecture Checkup · fedoroff-vlad bundle
Use when auditing whether a repo — or one change — conforms to AI-agent engineering standards: manifests (AGENTS.md, per-module agent manifests, Anthropic SKILL.md), SDD (spec-first), TDD / test strategy, change-propagation discipline, architecture canon + security doctrine, runtime / hardware fit, and secrets / config hygiene. Fires on: "архитектурный чекап", "architecture review", "проверь соответствие стандартам / манифестам / спецификации", "is the architecture canonical", "will it run on the target hardware", "проверь секреты / не утекло ли что-то", "are secrets safe in this repo", "audit the repo before a milestone". Produces a prioritized, evidence-linked findings report (🔴 blocker → 🟢 hygiene).

0 installs

14 published skills