- Home
- Skills
- Code Quality & Review
- Python Library Integration Review
Python Library Integration Review
Get location-backed findings and practical fixes for Python library integration problems.
Free
Works with the AI Agents you already use
Python Library Integration Review
Example session with this skill installed
Review this httpx usage: async def fetch(url): client = httpx.AsyncClient(); return await client.get(url). No wrapper closes the client. Give a compact report, not fixes.
- Read your context and instructions
- Compiled the python library integration
Reviewed fetch(url) for httpx lifecycle issues. No code changes made.
Compact Library Review
| Library | Version evidence | Scope |
|---|---|---|
| httpx | Not supplied | Client creation, request execution, and cleanup in fetch |
P1: HTTP client is not closed
| Detail | Finding |
|---|---|
| Location | fetch(url), from httpx.AsyncClient() through the return statement |
| Observed usage | Each call creates a client without a context manager or explicit close. You confirmed no wrapper handles cleanup. |
| Why it matters | Connections lack deterministic cleanup after success or failure. Repeated calls can accumulate open resources. |
| Recommendation | Use an async context manager for a per-call client. If reuse is needed, let an application-level owner manage the client and close it at shutdown. |
| Risk if unchanged | Repeated requests may cause resource pressure and operational failures. |
The request is correctly awaited. No blocking HTTP call is shown.
Limits: No dependency files, callers, or tests were supplied. Version compatibility and application-level behavior remain unverified. I have not flagged retries or timeout configuration without requirements or configuration evidence.
Next steps
- Choose per-call cleanup or application-owned reuse based on how
fetchis called. - Add tests confirming cleanup after both a successful request and a request exception.
Connects securely to your tools. The creator never sees your data.
About this skill
A Python app can use familiar libraries and still mishandle database sessions, background jobs, or HTTP clients. Get a focused review that points to concrete integration problems and recommends small, testable changes.
What it does
- Finds important libraries: Identifies actual usage in code and configuration, not just dependency lists.
- Checks version compatibility: Reviews library usage against detected versions and flags migration risks.
- Reviews integration boundaries: Examines how frameworks, validation, databases, workers, and clients work together.
- Pinpoints actionable issues: Gives code locations, practical consequences, and focused recommendations.
- Suggests follow-up work: Provides small review or fix requests with clear acceptance criteria.
How it works
- Ask your assistant to review an accessible Python repository.
- Optionally name libraries to prioritize or disable web research.
- Receive a dependency summary, review scope, prioritized findings, and follow-up suggestions.
- Request fixes separately if you want code changes.
Works with
Python repositories using libraries such as FastAPI, Django, SQLAlchemy, Pydantic, Alembic, Celery, httpx, pytest, LangChain, and LangGraph. It can consult official documentation for version-sensitive questions.
Why use this skill
Spend less time tracing library setup across application code, configuration, and tests. Recommendations account for existing project conventions and library versions, reducing unnecessary modernization work.
Use cases
- Check ORM sessions shared by requests and workers.
- Review validation and migration risks before an upgrade.
- Find HTTP client lifecycle gaps.
- Assess whether tests cover important integrations.
Known limitations
This is a focused Python library review, not a general architecture, security, or performance audit. Missing version evidence or unavailable documentation can limit conclusions.
Python library integration only, not a broad architecture, security, or performance audit. Reliable version-specific conclusions depend on repository evidence and available documentation.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
1 use
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 1 month ago
- Free with an Agensi account
Requires
Permissions
Reads Python source, dependency files, configuration, and tests and may run inspection commands. Browser/network access is for optional official documentation checks. Write access is conditional on a separate request for fixes; default review does not edit code.