Aiogram bot verify

Skill ballisarium/aiogram-bot-skills/skills/aiogram-bot-verify

focused workflows for building and maintaining aiogram bots

Install

npx -y skills add ballisarium/aiogram-bot-skills --skill aiogram-bot-verify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

use after changing aiogram bot code or when verification is requested; проверка, тесты, verify, syntax, imports, no polling, webhook, real token, or network.

SKILL.md

2.5 KB, as published. Nobody here has run it

aiogram bot verify

verify changed behavior with project-native commands. never start the bot, contact telegram, require real secrets, or mutate production.

workflow

discover commands from pyproject.toml, task files, test configuration, pre-commit, and CI. use README commands only when no stronger source exists.
select checks proportional to the changed area: focused tests first, then configured lint, format check, typecheck, and broader tests when warranted.
reject commands that start polling or a webhook server, use live external APIs, require production credentials, mutate production data, or run destructive migrations. require established fakes, mocks, or network blocking before running tests that could escape to external services.
compile and import relevant source, tests, router aggregation, and known consumers or entrypoint paths affected by shared-module changes. exclude virtual environments, caches, generated files, and build artifacts. imports must not trigger startup.
when touched, verify:
- router registration, filter boundaries, and handler imports
- callback packing, parsing, stale behavior, and callback answers
- FSM transitions and cleanup on success, cancel, and failure
- permissions and bot command registration
- repository behavior and migration presence, syntax, ordering, and execution against an isolated disposable database when the project provides a safe path
- startup or webhook configuration without launching it
if no test suite exists, run safe syntax and import checks, add a focused test when feasible, and state that behavior is not fully verified.
report only checks actually considered in a short matrix:

command or check	status	reason	action
`<command>`	PASS, FAIL, or SKIPPED	`<result or constraint>`	`<follow-up>`

use PASS only when a check ran and passed, FAIL when it ran and failed, and SKIPPED when it was unavailable, unsafe, out of scope, or not applicable. include the relevant error for failures and a concrete reason for skips.

completion requires truthful results for every relevant safe check and explicit disclosure of unverified behavior.

guardrails