Skip to content

Results for “change”

2 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…

Copilot
Coding & Development

Add clear comments and docstrings

Document existing code with helpful docstrings and comments that explain the why, not just the what.

0

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…

Copilot
Coding & Development

Git commit message and pull request description

Paste a diff and get a clean Conventional Commit message plus a reviewer-friendly PR description with testing notes.

0