Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

python-programming

Python development guidance for creating, modifying, reviewing, testing, packaging, and debugging Python code. Use when tasks involve .py files, pyproject.toml, requirements files, pytest, ruff, mypy, FastAPI, Django, Flask, CLIs, scripts, type hints, virtual environments, or Python dependency management.

Executar no Manus

Estrelas3

Forks0

Atualizado1 de maio de 2026 às 19:23

Fonte

devalexandre

devalexandre/Agno-Deep-Agents

Abrir repositório GitHub Ver repositórios do creator

Comando de instalação

Download

Executar no Manus

Útil paraSOC

Desenvolvedores de softwareInformática e Matemática15-1252L4

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	python-programming
description	Python development guidance for creating, modifying, reviewing, testing, packaging, and debugging Python code. Use when tasks involve .py files, pyproject.toml, requirements files, pytest, ruff, mypy, FastAPI, Django, Flask, CLIs, scripts, type hints, virtual environments, or Python dependency management.

Python Programming

Goal

Produce Python changes that fit the local project style, remain easy to test, and avoid surprising runtime behavior.

Discovery

Identify the Python version, package manager, and tooling from pyproject.toml, setup.cfg, setup.py, requirements*.txt, lockfiles, tox/nox config, and CI.
Check existing module layout before adding files.
Read nearby tests, fixtures, factories, and public API docs before changing behavior.
Preserve the project's existing framework choices, import style, typing level, and error handling conventions.

Implementation

Prefer straightforward functions and small classes over new abstractions.
Use pathlib, context managers, dataclasses, enums, and type hints when they match the surrounding code.
Keep import-time side effects out of modules; put executable script entry points behind if __name__ == "__main__":.
For async code, preserve the current event-loop model and avoid blocking calls inside coroutines.
For web apps, update schemas, route handlers, services, and tests together so request and response contracts stay aligned.
For packaging changes, keep dependencies minimal and update the right manifest or lockfile for the repo's chosen tool.

Verification

Prefer the narrowest relevant checks first: targeted pytest, then broader test suites when the change crosses modules.
Run configured formatters and linters such as ruff, black, isort, and mypy only when they are already part of the project.
When dependencies are unavailable, run syntax checks such as python -m py_compile <files> and explain the remaining gap.

Review Focus

Import cycles, hidden global state, mutable defaults, broad exception catches, sync/async mismatches, unclosed files, and compatibility with the configured Python version.

Mais deste repositório

mesmo repositório

elixir-programming

devalexandre/Agno-Deep-Agents

Elixir development guidance for creating, modifying, reviewing, testing, and debugging Elixir and Phoenix applications. Use when tasks involve .ex or .exs files, mix.exs, Phoenix, LiveView, Ecto, OTP supervision trees, GenServer, ExUnit, mix format, mix test, migrations, schemas, contexts, or Elixir dependency management.

2026-05-013

go-programming

devalexandre/Agno-Deep-Agents

Go development guidance for creating, modifying, reviewing, testing, and debugging Go services, libraries, CLIs, and tooling. Use when tasks involve .go files, go.mod, go.work, goroutines, channels, contexts, HTTP handlers, database code, table tests, gofmt, go test, or Go module management.

2026-05-013

node-programming

devalexandre/Agno-Deep-Agents

Node.js and JavaScript/TypeScript development guidance for creating, modifying, reviewing, testing, packaging, and debugging backend, CLI, tooling, and full-stack code. Use when tasks involve package.json, npm, pnpm, yarn, bun, .js, .mjs, .cjs, .ts, tsconfig, Express, NestJS, Next.js API routes, Vitest, Jest, ESLint, or Node dependency management.

2026-05-013

rust-programming

devalexandre/Agno-Deep-Agents

Rust development guidance for creating, modifying, reviewing, testing, packaging, and debugging Rust crates, CLIs, services, and libraries. Use when tasks involve .rs files, Cargo.toml, Cargo.lock, workspaces, ownership, lifetimes, traits, async Rust, tokio, serde, cargo fmt, cargo test, cargo clippy, or Rust dependency management.

2026-05-013

codebase-analysis

devalexandre/Agno-Deep-Agents

Analyze a codebase before changing it, infer local patterns, and choose focused implementation and verification steps.

2026-04-263

deep-agent-planning

devalexandre/Agno-Deep-Agents

Planning discipline for long-running Deep Agent tasks with delegation, task tracking, validation, and concise delivery.

2026-04-263

Python Programming

Goal

Produce Python changes that fit the local project style, remain easy to test, and avoid surprising runtime behavior.

Discovery

Identify the Python version, package manager, and tooling from pyproject.toml, setup.cfg, setup.py, requirements*.txt, lockfiles, tox/nox config, and CI.

Check existing module layout before adding files.

Read nearby tests, fixtures, factories, and public API docs before changing behavior.

Preserve the project's existing framework choices, import style, typing level, and error handling conventions.

Implementation

Prefer straightforward functions and small classes over new abstractions.

Use pathlib, context managers, dataclasses, enums, and type hints when they match the surrounding code.

Keep import-time side effects out of modules; put executable script entry points behind if __name__ == "__main__":.

For async code, preserve the current event-loop model and avoid blocking calls inside coroutines.

For web apps, update schemas, route handlers, services, and tests together so request and response contracts stay aligned.

For packaging changes, keep dependencies minimal and update the right manifest or lockfile for the repo's chosen tool.

Verification

Prefer the narrowest relevant checks first: targeted pytest, then broader test suites when the change crosses modules.

Run configured formatters and linters such as ruff, black, isort, and mypy only when they are already part of the project.

When dependencies are unavailable, run syntax checks such as python -m py_compile <files> and explain the remaining gap.

Review Focus

Import cycles, hidden global state, mutable defaults, broad exception catches, sync/async mismatches, unclosed files, and compatibility with the configured Python version.