Code generation, debugging and documentation
4 prompts
Add documentation to the code below. Language: [language] Docstring style: [Google / NumPy / JSDoc / PHPDoc] Rules: - Add a docstring to every public function/class: purpose, parameters, return value, exceptions, example - Add inline comments only where logic isn't obvious, explaining WHY - Don't change any behaviour…
Document existing code with helpful docstrings and comments that explain the why, not just the what.
Create a GitHub Actions workflow for my project. Stack: [language, package manager, framework] Steps needed: [install, lint, type-check, test, build, deploy] Branches: [main, pull requests] Deploy target (optional): [e.g. Vercel, server via SSH, Docker registry] Requirements: - Cache dependencies - Run tests on [versi…
Set up a GitHub Actions workflow that installs, lints, tests and builds your project on every push and pull request.
Based on the diff below, write: 1. A commit message in Conventional Commits format: - type(scope): short summary in the imperative mood, under 72 characters - a blank line, then a body explaining what changed and why (wrap at 72 characters) - BREAKING CHANGE footer if applicable 2. A pull request description with: - S…
Paste a diff and get a clean Conventional Commit message plus a reviewer-friendly PR description with testing notes.
Write unit tests for the function below. Language: [language] Testing framework: [e.g. Jest, pytest, PHPUnit, JUnit] Cover: - Typical inputs (happy path) - Edge cases: empty, zero, null/None, very large values, unusual characters - Invalid inputs and expected errors - Any branches or conditions in the code Rules: - On…
Generate thorough unit tests that cover normal cases, edge cases and errors, using your testing framework of choice.