Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

run-tests-and-fix

Étoiles19

Forks6

Mis à jour23 février 2026 à 06:59

Run the full test suite (backend pytest and frontend lint/test), then systematically fix any failures. Use when verifying changes or after pulling updates.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

quanwangniuniu

quanwangniuniu/marketing-simplified

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	run-tests-and-fix
description	Run the full test suite (backend pytest and frontend lint/test), then systematically fix any failures. Use when verifying changes or after pulling updates.

Run Tests and Fix Failures

When to Use

User asks to run tests, fix test failures, or verify the test suite.
User mentions CI failures, flaky tests, or getting tests green.
Task involves validating or repairing backend or frontend tests.

Context

Follow .cursor/AGENTS.md (Testing section) for commands and test file conventions. Backend tests live in backend/<app>/tests/; frontend in frontend/src/__tests__/.
Use any user-provided context (e.g. "backend", "frontend", or a path like task/tests) to run only that subset and fix failures there.

Instructions

Run backend tests: From repo root with stack up: docker compose exec backend pytest. With coverage: docker compose exec backend pytest --cov. Capture output and note failures.
Run frontend checks: From frontend/: npm run lint, then npm run test (or npm run test:ci for CI mode). Note any lint or test failures.
Analyze failures: Categorize by type (flaky, broken, new). Prioritize by impact. Check if failures relate to recent changes.
Fix systematically: Fix one issue at a time. Prefer the most critical or blocking failures first. Re-run the affected suite after each fix.
Re-run full suite: After fixes, run both backend pytest and frontend lint + test again to confirm everything passes.

Commands Reference

Backend: docker compose exec backend pytest (from repo root).
Frontend lint: npm run lint (from frontend/).
Frontend test: npm run test or npm run test:ci (from frontend/).

Plus depuis ce dépôt

même dépôt

add-backend-endpoint

quanwangniuniu/marketing-simplified

Implement a new backend API endpoint using the full chain (model, serializer, service, view, url, tests). Use when adding a new resource or action to an existing or new Django app.

2026-02-2319

add-frontend-page

quanwangniuniu/marketing-simplified

Implement a new frontend page and wire it to the backend API (API client, types, route, components, navigation, tests). Use when adding a new screen or feature that talks to the API.

2026-02-2319

code-review-checklist

quanwangniuniu/marketing-simplified

Run a code review against MediaJira standards (thin views/pages, API layer placement, no secrets, error handling, permissions, tests). Use before requesting review or merging.

2026-02-2319

create-pr

quanwangniuniu/marketing-simplified

Prepare a well-structured pull request with Conventional Commits, Jira key support, clear description, and pre-merge checks. Use when changes are ready for review.

2026-02-2319

security-audit

quanwangniuniu/marketing-simplified

Perform a security pass aligned with MediaJira standards (no secrets, auth/CORS, input validation, least privilege, credential handling). Use for pre-release checks or when touching auth/sensitive code.

2026-02-2319

name	run-tests-and-fix
description	Run the full test suite (backend pytest and frontend lint/test), then systematically fix any failures. Use when verifying changes or after pulling updates.

Run Tests and Fix Failures

When to Use

User asks to run tests, fix test failures, or verify the test suite.
User mentions CI failures, flaky tests, or getting tests green.
Task involves validating or repairing backend or frontend tests.

Context

Follow .cursor/AGENTS.md (Testing section) for commands and test file conventions. Backend tests live in backend/<app>/tests/; frontend in frontend/src/__tests__/.
Use any user-provided context (e.g. "backend", "frontend", or a path like task/tests) to run only that subset and fix failures there.

Instructions

Run backend tests: From repo root with stack up: docker compose exec backend pytest. With coverage: docker compose exec backend pytest --cov. Capture output and note failures.
Run frontend checks: From frontend/: npm run lint, then npm run test (or npm run test:ci for CI mode). Note any lint or test failures.
Analyze failures: Categorize by type (flaky, broken, new). Prioritize by impact. Check if failures relate to recent changes.
Fix systematically: Fix one issue at a time. Prefer the most critical or blocking failures first. Re-run the affected suite after each fix.
Re-run full suite: After fixes, run both backend pytest and frontend lint + test again to confirm everything passes.

Commands Reference

Backend: docker compose exec backend pytest (from repo root).
Frontend lint: npm run lint (from frontend/).
Frontend test: npm run test or npm run test:ci (from frontend/).