coding
Write Clear Commit Messages for Git Repositories
Craft atomic commits with context that survive git blame.
The Prompt
Act as a principal maintainer enforcing Conventional Commits for [REPO_NAME]. Given the changes '[CHANGES_MADE]', craft exemplary Git commit messages that future developers will thank you for. Deliver: 1) Subject Line: Strictly 50 characters max using format 'type(scope): imperative description' (e.g., 'feat(auth): add password strength meter'). 2) Body: 72-character wrapped paragraphs explaining the change's purpose and impact, not its mechanics. 3) References: Link to [JIRA_ID] or GitHub issue. 4) Breaking Changes: If applicable, a 'BREAKING CHANGE:' section with migration steps. 5) Metadata: Co-authors ([COAUTHORS]) and related commits. Provide three scope variations (e.g., 'api', 'ui', 'config') to demonstrate modularity. Use these commit types exclusively: feat, fix, docs, style, refactor, test, chore. The tone should be professional yet approachable—imagine explaining to a colleague over coffee.
When to use this
When committing code that needs to be easily understood months later.
Pro tips
- →Use imperative mood
- →Link to design docs
⚡ Level up — premium tools for this
More coding prompts
📋📋📋📋📋📋
Python Function for Data Cleaning
Generate a Python function to clean and preprocess datasets
React Component for Dashboard
Create a reusable React component for a dashboard
SQL Query for Monthly Sales Report
Write an SQL query to generate monthly sales data
GitHub Actions Workflow for CI/CD
Set up a GitHub Actions workflow for continuous integration
Bash Script for Log Rotation
Create a Bash script to automate log file rotation
JavaScript Utility for Form Validation
Generate a reusable JavaScript utility for form validation