If you have been using Grammarly for writing assistance and want to explore ChatGPT as an alternative editing tool, this guide will help you migrate your workflow effectively. Both tools serve similar purposes but operate differently, and understanding these differences will help you transition smoothly.
Why Consider ChatGPT for Editing
Grammarly provides real-time suggestions as you type, while ChatGPT offers more flexibility through conversational editing. For developers and power users, ChatGPT provides several advantages: you can paste entire documents for bulk review, request specific types of edits, and even create custom editing prompts that match your preferences.
The key difference lies in control. Grammarly applies rules automatically, whereas ChatGPT follows your instructions. This means you can ask ChatGPT to focus on specific aspects like tone, clarity, or technical terminology without getting distracted by minor grammar issues.
Setting Up Your Editing Prompts
The foundation of using ChatGPT effectively for editing is creating reusable prompts. Store these prompts in your notes or a simple text file for quick access.
Basic Editing Prompt
Review the following text for grammar, clarity, and conciseness.
Provide specific suggestions for improvement:
[PASTE YOUR TEXT HERE]
Developer-Focused Prompt
When editing technical content, developers often need specific attention to code references and terminology:
Edit this technical documentation for clarity and accuracy.
Maintain any code snippets exactly as written.
Flag any potentially confusing technical terms:
[PASTE YOUR TEXT HERE]
Tone Adjustment Prompt
Different writing contexts require different tones. Use this prompt to adapt your content:
Rewrite this text to be more conversational while maintaining professionalism.
Keep technical terms precise:
Automating Your Workflow
Developers can integrate ChatGPT into their existing workflows using simple scripts. Here is a bash function that sends selected text to ChatGPT via the command line:
#!/bin/bash
# Send selected text to ChatGPT for editing
# Requires OPENAI_API_KEY to be set
edit_with_chatgpt() {
if [ -z "$1" ]; then
echo "Usage: edit_with_chatgpt 'text to edit'"
return 1
fi
response=$(curl -s https://api.openai.com/v1/chat/completions \
-H "Authorization: Bearer $OPENAI_API_KEY" \
-H "Content-Type: application/json" \
-d "{
\"model\": \"gpt-4\",
\"messages\": [{\"role\": \"user\", \"content\": \"Edit this text for grammar and clarity: $1\"}],
\"temperature\": 0.3
}")
echo "$response" | jq -r '.choices[0].message.content'
}
Add this to your .bashrc or .zshrc to use it in your terminal.
Creating a VS Code Extension Workflow
For developers who work primarily in VS Code, consider using the ChatGPT extension. Configure it with a custom system prompt that matches your editing preferences:
{
"chatgpt.prompts": [
{
"name": "Quick Edit",
"prompt": "Edit the selected text for grammar, spelling, and clarity. Keep changes minimal and preserve the author's voice."
},
{
"name": "Technical Review",
"prompt": "Review this technical content for accuracy. Preserve code snippets and API references exactly as written. Suggest improvements for technical clarity."
}
]
}
This configuration allows you to highlight text and apply specific editing styles with keyboard shortcuts.
Comparing Results
When migrating from Grammarly, expect different output characteristics. Grammarly typically provides inline suggestions with specific replacements. ChatGPT returns revised passages with explanations. Here is a comparison:
Original text:
The software have many features that helps developers to be more productive.
Grammarly suggestion:
The software has many features that help developers be more productive.
ChatGPT response:
The software has many features that help developers become more productive.
Changes made:
- "have" → "has" (subject-verb agreement)
- "helps" → "help" (parallel structure)
- "to be more productive" → "become more productive" (more concise)
ChatGPT explains its changes, which helps you learn and improve your writing over time.
Handling Different Content Types
Your editing approach should vary based on content type. Here are specific recommendations:
Code comments and documentation: Request ChatGPT to preserve technical accuracy while improving readability. Include relevant context about the programming language or framework in your prompt.
Emails and messages: Ask for tone adjustments explicitly. A prompt like “Make this email more polite but direct” produces different results than a general grammar check.
Technical tutorials: Specify your target audience. A prompt mentioning “intermediate Python developers” will produce different terminology choices than one aimed at beginners.
Best Practices for Migration
Start by using both tools simultaneously during your transition period. Compare results and note where ChatGPT excels for your specific use cases. Build a collection of prompts that work well for your common editing scenarios.
Keep your API usage in mind if you use ChatGPT extensively. Setting usage limits and monitoring costs helps prevent unexpected charges. The free tier through chat.openai.com works for occasional editing but becomes limiting for heavy users.
Pay attention to how ChatGPT handles sensitive information. Avoid pasting confidential data into public ChatGPT interfaces. Consider using API-based solutions or the desktop application for sensitive work.
Related Reading
Built by theluckystrike — More at zovo.one