Telegram debugging

Skill ballisarium/aiogram-bot-skills/skills/telegram-debugging

focused workflows for building and maintaining aiogram bots

Install

npx -y skills add ballisarium/aiogram-bot-skills --skill telegram-debugging

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 when diagnosing or fixing a telegram or aiogram bot bug; баг, не работает, handler missing, filters, callbacks, stuck FSM, edit, webhook, API errors.

SKILL.md

2.1 KB, as published. Nobody here has run it

telegram debugging

reproduce or narrow the failure before changing code. fix the root cause without unrelated refactoring.

workflow

establish the user action, expected and actual behavior, chat type, event or command, current state, aiogram version, recent changes, and relevant logs or traceback.
make a focused test fail on the reported behavior before the fix. use an existing test when it proves the symptom; otherwise create the smallest regression test when feasible.
classify the failure: registration or filter mismatch, callback payload or answer, FSM transition or cleanup, stale data, message edit, startup mode, middleware dependency, permission, race or double action, or telegram API handling.
trace routing end to end: router inclusion and order, exact filters, command or callback prefix, state constraints, catch-all handlers, and middleware.
trace data and state end to end: service inputs, repository query, transaction lifecycle, entity freshness, permissions, idempotency, and cleanup.
for webhook or polling failures, confirm one startup mode, the real entrypoint, config loading, lifecycle hooks, and import safety.
change the smallest area that explains the evidence. do not swallow telegram exceptions or repair the visible response while leaving state or data corrupt.
add regression coverage for the failed route, payload, transition, stale entity, exception, or repeated action.
use telegram-docs-check when an API exception, retry rule, signature, or payload contract is version-sensitive.
use aiogram-bot-verify after code changes.

completion requires an evidence-backed root cause, a minimal fix, regression coverage or a stated reason it is infeasible, and safe verification.

guardrails