DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check backend and frontend health before editing code with Agent Py

Run the full verification suite so changes to agents, APIs, or the UI can be checked.

Who it is forA contributor about to change the FastAPI backend, the shared API contracts, or the Vue frontend.

The problemWithout a baseline, it is hard to tell whether a failure came from your edit or from the existing code.

The outcomeA recorded pass or fail result for each check, giving you a clean baseline before any change.

What you need first

  • Python 3.10+, uv, Node.js 22+, and Docker Compose installed locally
  • Access to a configured Qwen-compatible model service and its API key
  • Tencent CLS credentials if you use the CLS integration
  • Git clone of kkjiangk/agent-py

Steps

  1. Run cd apps/backend and then uv sync --frozen.
  2. Run uv run ruff check ., uv run pyright, and uv run pytest inside apps/backend.
  3. Return to the repository root and run npm run contracts:typecheck and npm --workspace packages/api-contracts test.
  4. Run npm run frontend:typecheck, npm run frontend:test, and npm run frontend:build.
  5. Run python3 scripts/check_frontend_bundle.py and npm audit --audit-level=moderate.

Prompt for your agent

In the kkjiangk/agent-py repository, run the backend and frontend verification commands listed in the README Verification section. Report the pass or fail result of each command. Verify that the backend pytest run has no failures before you propose any edit.

Caveat. The README's local results are dated 2026-10-04 and do not show that a GitHub-hosted CI run or an AWS deployment has completed.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page