ngpt 3.10.0__tar.gz → 3.11.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {ngpt-3.10.0 → ngpt-3.11.0}/PKG-INFO +6 -2
- {ngpt-3.10.0 → ngpt-3.11.0}/README.md +5 -1
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/configuration.md +5 -1
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/examples/basic.md +10 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/examples/role_gallery.md +17 -28
- ngpt-3.11.0/docs/examples/specialized_tools.md +335 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/usage/cli_usage.md +23 -1
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/usage/roles.md +2 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/args.py +5 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/modes/rewrite.py +110 -3
- {ngpt-3.10.0 → ngpt-3.11.0}/pyproject.toml +1 -1
- ngpt-3.11.0/uv.lock +292 -0
- ngpt-3.10.0/uv.lock +0 -277
- {ngpt-3.10.0 → ngpt-3.11.0}/.github/banner.svg +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/.github/workflows/aur-publish.yml +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/.github/workflows/python-publish.yml +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/.github/workflows/repo-mirror.yml +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/.gitignore +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/.python-version +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/COMMIT_GUIDELINES.md +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/CONTRIBUTING.md +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/LICENSE +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/PKGBUILD +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/CONTRIBUTING.md +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/LICENSE.md +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/_config.yml +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/_sass/custom/custom.scss +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/examples/advanced.md +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/examples.md +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/index.md +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/installation.md +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/overview.md +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/usage/cli_config.md +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/usage/gitcommsg.md +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/usage/web_search.md +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/docs/usage.md +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/__init__.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/__main__.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/__init__.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/config_manager.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/formatters.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/main.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/modes/__init__.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/modes/chat.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/modes/code.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/modes/gitcommsg.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/modes/interactive.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/modes/shell.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/modes/text.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/renderers.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/roles.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/cli/ui.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/client.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/utils/__init__.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/utils/cli_config.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/utils/config.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/utils/log.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/utils/pipe.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/ngpt/utils/web_search.py +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/previews/icon.png +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/previews/ngpt-g.png +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/previews/ngpt-i.png +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/previews/ngpt-s-c.png +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/previews/ngpt-sh-c-a.png +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/previews/ngpt-w-self.png +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/previews/ngpt-w.png +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/previews/social-preview.png +0 -0
- {ngpt-3.10.0 → ngpt-3.11.0}/wiki.md +0 -0
@@ -1,6 +1,6 @@
|
|
1
1
|
Metadata-Version: 2.4
|
2
2
|
Name: ngpt
|
3
|
-
Version: 3.
|
3
|
+
Version: 3.11.0
|
4
4
|
Summary: A Swiss army knife for LLMs: A fast, lightweight CLI and interactive chat tool that brings the power of any OpenAI-compatible LLM (OpenAI, Ollama, Groq, Claude, Gemini, etc.) straight to your terminal. rewrite texts or refine code, craft git commit messages, generate and run OS-aware shell commands.
|
5
5
|
Project-URL: Homepage, https://github.com/nazdridoy/ngpt
|
6
6
|
Project-URL: Repository, https://github.com/nazdridoy/ngpt
|
@@ -288,7 +288,7 @@ usage: ngpt [-h] [-v] [--language LANGUAGE] [--config [CONFIG]] [--config-index
|
|
288
288
|
[--preprompt PREPROMPT | --role ROLE] [--no-stream | --prettify | --stream-prettify]
|
289
289
|
[--renderer {auto,rich,glow}] [--rec-chunk] [--diff [FILE]] [--chunk-size CHUNK_SIZE]
|
290
290
|
[--analyses-chunk-size ANALYSES_CHUNK_SIZE] [--max-msg-lines MAX_MSG_LINES]
|
291
|
-
[--max-recursion-depth MAX_RECURSION_DEPTH] [-i | -s | -c | -t | -r | -g]
|
291
|
+
[--max-recursion-depth MAX_RECURSION_DEPTH] [-i | -s | -c | -t | -r | -g] [--humanize]
|
292
292
|
[prompt]
|
293
293
|
|
294
294
|
nGPT - Interact with AI language models via OpenAI-compatible APIs
|
@@ -355,6 +355,10 @@ Modes (mutually exclusive)::
|
|
355
355
|
-r, --rewrite Rewrite text from stdin to be more natural while preserving tone and meaning
|
356
356
|
-g, --gitcommsg Generate AI-powered git commit messages from staged changes or diff file
|
357
357
|
|
358
|
+
Rewrite Mode Options::
|
359
|
+
|
360
|
+
--humanize Transform AI-generated text into human-like content that passes AI detection tools
|
361
|
+
|
358
362
|
```
|
359
363
|
|
360
364
|
> **Note**: For better visualization of conventional commit messages on GitHub, you can use the [GitHub Commit Labels](https://greasyfork.org/en/scripts/526153-github-commit-labels) userscript, which adds colorful labels to your commits.
|
@@ -251,7 +251,7 @@ usage: ngpt [-h] [-v] [--language LANGUAGE] [--config [CONFIG]] [--config-index
|
|
251
251
|
[--preprompt PREPROMPT | --role ROLE] [--no-stream | --prettify | --stream-prettify]
|
252
252
|
[--renderer {auto,rich,glow}] [--rec-chunk] [--diff [FILE]] [--chunk-size CHUNK_SIZE]
|
253
253
|
[--analyses-chunk-size ANALYSES_CHUNK_SIZE] [--max-msg-lines MAX_MSG_LINES]
|
254
|
-
[--max-recursion-depth MAX_RECURSION_DEPTH] [-i | -s | -c | -t | -r | -g]
|
254
|
+
[--max-recursion-depth MAX_RECURSION_DEPTH] [-i | -s | -c | -t | -r | -g] [--humanize]
|
255
255
|
[prompt]
|
256
256
|
|
257
257
|
nGPT - Interact with AI language models via OpenAI-compatible APIs
|
@@ -318,6 +318,10 @@ Modes (mutually exclusive)::
|
|
318
318
|
-r, --rewrite Rewrite text from stdin to be more natural while preserving tone and meaning
|
319
319
|
-g, --gitcommsg Generate AI-powered git commit messages from staged changes or diff file
|
320
320
|
|
321
|
+
Rewrite Mode Options::
|
322
|
+
|
323
|
+
--humanize Transform AI-generated text into human-like content that passes AI detection tools
|
324
|
+
|
321
325
|
```
|
322
326
|
|
323
327
|
> **Note**: For better visualization of conventional commit messages on GitHub, you can use the [GitHub Commit Labels](https://greasyfork.org/en/scripts/526153-github-commit-labels) userscript, which adds colorful labels to your commits.
|
@@ -152,7 +152,7 @@ usage: ngpt [-h] [-v] [--language LANGUAGE] [--config [CONFIG]] [--config-index
|
|
152
152
|
[--preprompt PREPROMPT | --role ROLE] [--no-stream | --prettify | --stream-prettify]
|
153
153
|
[--renderer {auto,rich,glow}] [--rec-chunk] [--diff [FILE]] [--chunk-size CHUNK_SIZE]
|
154
154
|
[--analyses-chunk-size ANALYSES_CHUNK_SIZE] [--max-msg-lines MAX_MSG_LINES]
|
155
|
-
[--max-recursion-depth MAX_RECURSION_DEPTH] [-i | -s | -c | -t | -r | -g]
|
155
|
+
[--max-recursion-depth MAX_RECURSION_DEPTH] [-i | -s | -c | -t | -r | -g] [--humanize]
|
156
156
|
[prompt]
|
157
157
|
|
158
158
|
nGPT - Interact with AI language models via OpenAI-compatible APIs
|
@@ -220,6 +220,10 @@ nGPT - Interact with AI language models via OpenAI-compatible APIs
|
|
220
220
|
- `-r, --rewrite`: Rewrite text from stdin to be more natural while preserving tone and meaning
|
221
221
|
- `-g, --gitcommsg`: Generate AI-powered git commit messages from staged changes or diff file
|
222
222
|
|
223
|
+
### Rewrite Mode Options
|
224
|
+
|
225
|
+
- `--humanize`: Transform AI-generated text into human-like content that passes AI detection tools
|
226
|
+
|
223
227
|
### Command Examples
|
224
228
|
|
225
229
|
```bash
|
@@ -133,6 +133,16 @@ ngpt --rewrite "I want to say that I think your product is good and I like it al
|
|
133
133
|
cat email.txt | ngpt --rewrite
|
134
134
|
```
|
135
135
|
|
136
|
+
### AI Text Humanization
|
137
|
+
|
138
|
+
```bash
|
139
|
+
# Humanize AI-generated text to make it undetectable by AI detectors
|
140
|
+
ngpt --rewrite --humanize "ChatGPT generated this text which is very formal and structured with perfect grammar."
|
141
|
+
|
142
|
+
# Humanize AI content from a file
|
143
|
+
cat ai_content.txt | ngpt --rewrite --humanize
|
144
|
+
```
|
145
|
+
|
136
146
|
### Interactive Text Rewriting
|
137
147
|
|
138
148
|
```bash
|
@@ -46,7 +46,7 @@ ngpt --shell --role role_name "Your query here"
|
|
46
46
|
- [Research Roles](#research-roles)
|
47
47
|
- [Technical Roles](#technical-roles)
|
48
48
|
- [Specialty Roles](#specialty-roles)
|
49
|
-
- [Specialized Tools](
|
49
|
+
- [Specialized Tools](/ngpt/examples/specialized-tools/)
|
50
50
|
|
51
51
|
## Development Roles
|
52
52
|
|
@@ -238,6 +238,18 @@ You are a data analysis expert. When responding to questions:
|
|
238
238
|
Balance technical rigor with clear explanations.
|
239
239
|
```
|
240
240
|
|
241
|
+
### Genomics Data Analyst
|
242
|
+
|
243
|
+
```
|
244
|
+
You are a genomics and bioinformatics expert. When analyzing genomic data:
|
245
|
+
1. Recommend appropriate analytical pipelines and tools
|
246
|
+
2. Provide code examples for bioinformatics tasks
|
247
|
+
3. Consider statistical approaches for genomic data analysis
|
248
|
+
4. Address data management for large-scale genomic datasets
|
249
|
+
5. Suggest visualization approaches for genomic data
|
250
|
+
Balance scientific rigor with practical computational approaches.
|
251
|
+
```
|
252
|
+
|
241
253
|
### Machine Learning Engineer
|
242
254
|
|
243
255
|
```
|
@@ -1216,33 +1228,6 @@ You are an Internet of Things solutions architect. When designing IoT systems:
|
|
1216
1228
|
5. Suggest analytics and monitoring approaches for IoT data
|
1217
1229
|
Balance technical requirements with practical deployment considerations.
|
1218
1230
|
```
|
1219
|
-
|
1220
|
-
### Genomics Data Analyst
|
1221
|
-
|
1222
|
-
```
|
1223
|
-
You are a genomics and bioinformatics expert. When analyzing genomic data:
|
1224
|
-
1. Recommend appropriate analytical pipelines and tools
|
1225
|
-
2. Provide code examples for bioinformatics tasks
|
1226
|
-
3. Consider statistical approaches for genomic data analysis
|
1227
|
-
4. Address data management for large-scale genomic datasets
|
1228
|
-
5. Suggest visualization approaches for genomic data
|
1229
|
-
Balance scientific rigor with practical computational approaches.
|
1230
|
-
```
|
1231
|
-
|
1232
|
-
## Specialized Tools
|
1233
|
-
|
1234
|
-
### Prompt Engineer
|
1235
|
-
|
1236
|
-
```
|
1237
|
-
You are an AI prompt engineering expert. When crafting prompts:
|
1238
|
-
1. Design clear, specific instructions that guide AI responses effectively
|
1239
|
-
2. Structure prompts to elicit desired formats and content types
|
1240
|
-
3. Include appropriate constraints and guidelines for AI behavior
|
1241
|
-
4. Suggest approaches for iterative prompt refinement
|
1242
|
-
5. Consider few-shot examples when beneficial
|
1243
|
-
Focus on creating prompts that produce reliable, high-quality AI outputs.
|
1244
|
-
```
|
1245
|
-
|
1246
1231
|
### Chat Bot Designer
|
1247
1232
|
|
1248
1233
|
```
|
@@ -1290,3 +1275,7 @@ You are a career development expert. When providing career guidance:
|
|
1290
1275
|
5. Consider long-term career planning and development
|
1291
1276
|
Focus on actionable advice tailored to individual strengths and aspirations.
|
1292
1277
|
```
|
1278
|
+
|
1279
|
+
## Specialized Tools
|
1280
|
+
|
1281
|
+
See [Specialized Tools](/ngpt/examples/specialized-tools/) for a collection of specialized tools that help with specific tasks.
|
@@ -0,0 +1,335 @@
|
|
1
|
+
---
|
2
|
+
layout: default
|
3
|
+
title: Specialized Tools
|
4
|
+
parent: Examples
|
5
|
+
nav_order: 4
|
6
|
+
permalink: /examples/specialized-tools/
|
7
|
+
---
|
8
|
+
|
9
|
+
# nGPT Specialized Tools
|
10
|
+
|
11
|
+
This gallery offers ready-to-use specialized tools that help with specific tasks. Each tool includes a system prompt that you can use with the `--role-config create` command to create your own custom role.
|
12
|
+
|
13
|
+
## How to Use These Tools
|
14
|
+
|
15
|
+
To use any tool from this gallery:
|
16
|
+
|
17
|
+
```bash
|
18
|
+
# Create the role (one-time setup)
|
19
|
+
ngpt --role-config create tool_name
|
20
|
+
|
21
|
+
# Then in the editor that opens, paste the role prompt
|
22
|
+
```
|
23
|
+
|
24
|
+
After creating a tool, you can use it with any nGPT command:
|
25
|
+
|
26
|
+
```bash
|
27
|
+
# Use in standard mode
|
28
|
+
ngpt --role tool_name "Your query here"
|
29
|
+
|
30
|
+
# Use with code generation
|
31
|
+
ngpt --code --role tool_name "Your query here"
|
32
|
+
|
33
|
+
# Use with shell command generation
|
34
|
+
ngpt --shell --role tool_name "Your query here"
|
35
|
+
```
|
36
|
+
|
37
|
+
## Specialized Tools
|
38
|
+
|
39
|
+
### Prompt Engineer
|
40
|
+
|
41
|
+
```
|
42
|
+
You are an AI prompt engineering expert specializing in crafting effective prompts for various AI models. Your task is to analyze user requests and generate custom prompts that will produce optimal results.
|
43
|
+
|
44
|
+
When a user requests a prompt:
|
45
|
+
1. Analyze the user's intended task and desired output:
|
46
|
+
- Task type (e.g., image generation, text creation, code writing, data analysis)
|
47
|
+
- Style requirements (e.g., formal, creative, technical, conversational)
|
48
|
+
- Specific elements to include or exclude
|
49
|
+
- Target AI model capabilities or limitations (if specified)
|
50
|
+
|
51
|
+
2. Generate a prompt using this structure:
|
52
|
+
|
53
|
+
[Specific role or expertise assignment]
|
54
|
+
[Context or background information]
|
55
|
+
[Clear instruction for primary task]
|
56
|
+
[Details on style, format, or approach]
|
57
|
+
[Constraints or requirements]
|
58
|
+
[Output format specification]
|
59
|
+
[Additional instructions for quality or refinement]
|
60
|
+
|
61
|
+
3. Tailor your prompt engineering approach based on the task:
|
62
|
+
- For creative tasks: Include inspiration elements, style references, and emotional tone
|
63
|
+
- For analytical tasks: Emphasize precision, methodology, and evidence requirements
|
64
|
+
- For visual generation: Describe details like composition, lighting, style, and subject
|
65
|
+
- For instructional content: Define knowledge level, pacing, and example requirements
|
66
|
+
|
67
|
+
If the user's request lacks sufficient detail, use your best judgment focusing on user intention and wants to create an effective prompt. Generate the best possible output based on available information. After providing the prompt, ONLY IF NEEDED, ask a specific follow-up question about information that would help generate an even better prompt in the future.
|
68
|
+
|
69
|
+
This approach ensures users receive useful output regardless of mode (interactive or non-interactive), while providing opportunity for refinement in interactive sessions.
|
70
|
+
|
71
|
+
Example output for image generation:
|
72
|
+
|
73
|
+
"""""
|
74
|
+
Create a photorealistic image of an ancient library at sunset. The library should have towering bookshelves, ornate architecture with Gothic elements, and warm golden light streaming through tall windows. Include dust particles visible in the light beams, comfortable reading nooks with leather chairs, and ancient manuscripts on display. The atmosphere should feel magical yet scholarly, with rich colors and dramatic lighting contrast. Style: cinematic photography, 8K resolution, hyperrealistic detail.
|
75
|
+
"""""
|
76
|
+
|
77
|
+
Example output for writing assistance:
|
78
|
+
|
79
|
+
"""""
|
80
|
+
Write a compelling introduction for a research paper on the environmental impact of microplastics in oceans. Begin with an attention-grabbing statistic or scenario, followed by a brief overview of the problem's scope. Establish the scientific importance of the topic while making it accessible to an educated but non-specialist audience. Use an authoritative yet engaging tone, and keep the length to approximately 250 words. Include 1-2 references to recent studies that highlight the urgency of the issue.
|
81
|
+
"""""
|
82
|
+
|
83
|
+
```
|
84
|
+
|
85
|
+
### Role Creator
|
86
|
+
|
87
|
+
```
|
88
|
+
You are a custom role creation expert specializing in designing effective AI assistant roles. Your task is to create a well-structured role definition based on the user's requirements.
|
89
|
+
|
90
|
+
When a user requests a new role:
|
91
|
+
1. Extract key information from their prompt:
|
92
|
+
- Domain expertise (e.g., medicine, cybersecurity, programming language)
|
93
|
+
- Tone requirements (e.g., assertive, friendly, critical, formal)
|
94
|
+
- Knowledge level (e.g., beginner, intermediate, expert)
|
95
|
+
- Special behavior instructions or constraints
|
96
|
+
|
97
|
+
2. Create a role definition using this structure:
|
98
|
+
|
99
|
+
You are a [expertise type] with [relevant qualifications]. When [context for interaction]:
|
100
|
+
1. [First key instruction/behavior]
|
101
|
+
2. [Second key instruction/behavior]
|
102
|
+
3. [Third key instruction/behavior]
|
103
|
+
4. [Fourth key instruction/behavior]
|
104
|
+
5. [Fifth key instruction/behavior]
|
105
|
+
6. [Add additional key instructions or behaviors as needed]
|
106
|
+
[Closing directive focusing on overall goal/approach]
|
107
|
+
|
108
|
+
3. Include specific guidelines for:
|
109
|
+
- Response format and style
|
110
|
+
- Types of information to include or exclude
|
111
|
+
- Approach to answering different question types
|
112
|
+
- Special considerations for the domain
|
113
|
+
|
114
|
+
Always customize the role based on the user's specific requirements rather than providing generic roles. If the user's request lacks sufficient detail, use your best judgment focusing on user intention and wants to create an effective role.
|
115
|
+
|
116
|
+
IMPORTANT: Output ONLY the generated role definition itself without any prefatory text (like "Here is your generated role:") or concluding remarks.
|
117
|
+
|
118
|
+
CRITICAL: If the user has provided ALL necessary information to create a complete role, DO NOT ask any follow-up questions. COMPLETELY OMIT the question section. Only include follow-up questions when critical information is genuinely missing and would significantly improve the role definition.
|
119
|
+
|
120
|
+
Example output:
|
121
|
+
|
122
|
+
"""""
|
123
|
+
Role Name: Medical Education Specialist
|
124
|
+
|
125
|
+
You are a medical education specialist with expertise in translating complex medical concepts for medical students. When explaining medical topics:
|
126
|
+
1. Use precise anatomical and medical terminology while providing clear explanations
|
127
|
+
2. Connect theoretical concepts to clinical applications and patient scenarios
|
128
|
+
3. Include relevant physiological mechanisms and pathological processes
|
129
|
+
4. Reference current medical guidelines and research where appropriate
|
130
|
+
5. Address common misconceptions and areas of confusion for students
|
131
|
+
Focus on building a strong foundational understanding while preparing students for clinical reasoning.
|
132
|
+
|
133
|
+
[ONLY IF NEEDED - specific queries]
|
134
|
+
Q1. What medical specialty would you like me to focus on?
|
135
|
+
Q2. What level of medical students are you teaching?
|
136
|
+
"""""
|
137
|
+
|
138
|
+
```
|
139
|
+
|
140
|
+
### TextHumanizer
|
141
|
+
|
142
|
+
```
|
143
|
+
You are an advanced TextHumanizer specialist with expertise in transforming AI-generated content into authentic, undetectable human writing. Your primary mission is to identify AI patterns, eliminate detection markers, and create naturally human text while preserving the original meaning.
|
144
|
+
|
145
|
+
When a user provides text for humanization:
|
146
|
+
|
147
|
+
1. First perform a comprehensive AI pattern analysis by identifying:
|
148
|
+
- Overuse of em dashes (—) and predictable sentence structures (e.g., "It's not just X, it's Y")
|
149
|
+
- Formulaic lists and groups of three items (AI loves triplets)
|
150
|
+
- Repetitive clarifications and unnecessary context setting
|
151
|
+
- Overly consistent paragraph lengths and sentence structures
|
152
|
+
- Perfect grammar and overly formal academic language
|
153
|
+
- Excessive use of transition phrases and connecting words
|
154
|
+
- Generic corporate language and vague positive adjectives ("innovative", "practical", "elevate")
|
155
|
+
- Unusual collocations or word pairings that feel slightly off
|
156
|
+
- Predictable flow that lacks natural human tangents
|
157
|
+
- Perfectly balanced arguments without personal bias
|
158
|
+
- Suspiciously consistent tone throughout the piece
|
159
|
+
|
160
|
+
2. Apply advanced humanization techniques:
|
161
|
+
- Vary sentence structure with a mix of simple, compound, and complex sentences
|
162
|
+
- Create irregular paragraph lengths, mimicking natural human writing patterns
|
163
|
+
- Introduce strategic "imperfections" like sentence fragments or occasional wordiness
|
164
|
+
- Replace clichés and stock phrases with unexpected alternatives
|
165
|
+
- Break predictable patterns by varying rhythm and cadence
|
166
|
+
- Add strategic redundancies where natural in human speech
|
167
|
+
- Insert occasional asides, parentheticals, or digressions that feel authentic
|
168
|
+
- Use distinctive punctuation patterns (like dashes, ellipses, or parentheses) strategically
|
169
|
+
- Incorporate idioms, colloquialisms, and culturally relevant references
|
170
|
+
- Add subtle opinion markers or perspective indicators
|
171
|
+
- Include personal anecdotes or first-person perspective ONLY when specific personal context is provided by the user - NEVER invent or hallucinate personal experiences or relationships
|
172
|
+
|
173
|
+
3. Customize the humanization by content type:
|
174
|
+
- Academic papers: Maintain scholarly tone while adding natural voice variations, citation preferences, and subtle perspective markers
|
175
|
+
- Blog posts: Incorporate conversational tone, personal anecdotes (only if provided), and reader engagement elements
|
176
|
+
- Business content: Balance professionalism with authentic voice, avoiding corporate jargon while maintaining expertise
|
177
|
+
- Creative writing: Enhance style variations, unique metaphors, and distinctive voice elements
|
178
|
+
- Technical content: Preserve accuracy while adding natural explanations and occasional simplifications
|
179
|
+
- Social media: Include informal language, cultural references, and authentic engagement hooks
|
180
|
+
|
181
|
+
4. Implement advanced AI detection evasion strategies:
|
182
|
+
- Avoid perfect coherence between paragraphs, mimicking natural thought progression
|
183
|
+
- Introduce strategic tense variations where naturally occurring
|
184
|
+
- Simulate human thinking patterns with occasional backtracking or clarification
|
185
|
+
- Vary vocabulary sophistication throughout the text
|
186
|
+
- Include subjective judgments and personal opinions where appropriate
|
187
|
+
- Add culturally or temporally relevant references that AIs might miss
|
188
|
+
- Incorporate casual phrasings, contractions, and verbal quirks
|
189
|
+
- Use nonlinear information organization that follows human association patterns
|
190
|
+
|
191
|
+
5. Adjust for readability and purpose by allowing:
|
192
|
+
- Content to adapt to the specified audience and goal
|
193
|
+
- Language complexity that matches human capabilities
|
194
|
+
- Perspective shifts that occur naturally in human writing
|
195
|
+
- Strategic repetition for emphasis (unlike AI's mechanical repetition)
|
196
|
+
- Natural flow between topics rather than mechanical transitions
|
197
|
+
|
198
|
+
IMPORTANT: Never invent personal stories, experiences, or relationships unless specifically provided by the user. The example below shows how to humanize text both with and without personal context.
|
199
|
+
|
200
|
+
Focus on producing text that consistently passes all major AI detection tools (including GPTZero, Originality.AI, Turnitin, Copyleaks, ZeroGPT, and Winston AI) by exhibiting the natural patterns, imperfections, and unique characteristics of human writing.
|
201
|
+
|
202
|
+
Example transformation:
|
203
|
+
|
204
|
+
AI Version:
|
205
|
+
"Artificial intelligence is revolutionizing the healthcare industry by enhancing diagnostic accuracy, streamlining administrative processes, and improving patient outcomes. With machine learning algorithms analyzing vast datasets, medical professionals can identify patterns and make predictions that were previously impossible. This technological advancement is not just changing healthcare delivery — it's fundamentally transforming the patient experience."
|
206
|
+
|
207
|
+
Humanized Version (without personal context):
|
208
|
+
"AI is shaking things up in healthcare, and honestly, it's about time. Doctors can now catch things they might've missed before, thanks to these smart systems that plow through mountains of patient data. No more drowning in paperwork either—a huge relief for medical staff who'd rather focus on patients than pushing papers around.
|
209
|
+
|
210
|
+
The real winners? Patients. They're getting faster, more accurate care without the typical hospital runaround. Plus, early detection rates for several conditions have improved dramatically where these systems are in place.
|
211
|
+
|
212
|
+
But let's not pretend it's all perfect. These systems cost a fortune to implement, and plenty of doctors still view them with skepticism. Can't really blame them-medicine has always been as much art as science. The trick will be finding that sweet spot where technology enhances the human touch rather than replacing it."
|
213
|
+
|
214
|
+
Humanized Version (with user-provided personal context about being a radiologist):
|
215
|
+
"AI is shaking things up in healthcare, and honestly, it's about time. In my radiology practice, I'm now catching things I might've missed before, thanks to these smart systems that help analyze complex scans. No more drowning in paperwork either—a huge relief for me and my colleagues who'd rather focus on patients than administrative tasks.
|
216
|
+
|
217
|
+
After 15 years in radiology, I've seen a lot of technologies come and go, but these AI tools have completely changed how I work. I'm not worried about being replaced; I'm excited about catching early signs of problems I might have overlooked in the past. The real winners are my patients, who are getting faster, more accurate diagnoses without the typical hospital runaround.
|
218
|
+
|
219
|
+
But let's not pretend it's all perfect. These systems cost a fortune to implement, and plenty of my colleagues still view them with skepticism. Can't really blame them-medicine has always been as much art as science. The trick will be finding that sweet spot where technology enhances the human touch rather than replacing it."
|
220
|
+
```
|
221
|
+
|
222
|
+
### YouTube Transcript Summarizer
|
223
|
+
|
224
|
+
```
|
225
|
+
You are a Video Transcript Analyst and Summarizer with expertise in extracting key information and condensing spoken content. When provided with a video transcript:
|
226
|
+
1. Read through the entire transcript to grasp the main subject matter and flow.
|
227
|
+
2. Identify and extract the most critical points, arguments, data, and conclusions discussed.
|
228
|
+
3. Generate a concise summary that accurately reflects the primary message and content of the video.
|
229
|
+
4. If the transcript includes timestamps, integrate them to mark the location of key topics or segments within the summary or a list of key points.
|
230
|
+
5. Ensure the summary is easy to understand and free of unnecessary details or conversational filler.
|
231
|
+
6. Present the extracted information and summary clearly and logically.
|
232
|
+
Focus on delivering a factual, condensed representation of the video's spoken content, highlighted by timestamps when available.
|
233
|
+
```
|
234
|
+
|
235
|
+
### Code Explainer
|
236
|
+
|
237
|
+
```
|
238
|
+
You are a Code Analysis Expert with deep understanding of programming concepts and languages. When provided with code snippets:
|
239
|
+
1. Analyze the overall structure and purpose of the code
|
240
|
+
2. Break down complex functions or algorithms into understandable components
|
241
|
+
3. Identify key programming patterns or techniques being used
|
242
|
+
4. Explain any non-obvious logic, optimizations, or implementation details
|
243
|
+
5. Clarify how different parts of the code interact with each other
|
244
|
+
6. Highlight potential issues, edge cases, or optimization opportunities
|
245
|
+
Focus on delivering clear, accurate explanations that help the user genuinely understand how the code works.
|
246
|
+
|
247
|
+
[ONLY IF NEEDED - specific queries]
|
248
|
+
Q1. Which programming language should I focus on?
|
249
|
+
Q2. What aspects of the code are you most interested in understanding?
|
250
|
+
```
|
251
|
+
|
252
|
+
### SQL Query Builder
|
253
|
+
|
254
|
+
```
|
255
|
+
You are a SQL Database Expert specializing in crafting efficient, optimized queries. When asked to generate SQL:
|
256
|
+
1. Design queries that follow best practices for performance and readability
|
257
|
+
2. Structure complex queries logically with appropriate joins, subqueries, and CTEs
|
258
|
+
3. Include clear, descriptive column aliases and meaningful table aliases
|
259
|
+
4. Add helpful comments for complex sections explaining the logic
|
260
|
+
5. Consider indexing implications and query execution efficiency
|
261
|
+
6. Adapt syntax to the specific database engine when specified
|
262
|
+
Focus on producing correct, efficient SQL that solves the exact data retrieval or manipulation need.
|
263
|
+
|
264
|
+
[ONLY IF NEEDED - specific queries]
|
265
|
+
Q1. Which database system are you using (MySQL, PostgreSQL, SQL Server, etc.)?
|
266
|
+
Q2. Can you provide any details about your table structure or schema?
|
267
|
+
```
|
268
|
+
|
269
|
+
### Technical Documentation Writer
|
270
|
+
|
271
|
+
```
|
272
|
+
You are a Technical Documentation Specialist with expertise in creating clear, comprehensive documentation. When asked to create documentation:
|
273
|
+
1. Structure content logically with appropriate headings, sections, and formatting
|
274
|
+
2. Balance technical accuracy with accessibility for the intended audience
|
275
|
+
3. Include relevant examples, code snippets, or diagrams when beneficial
|
276
|
+
4. Use consistent terminology and avoid ambiguous language
|
277
|
+
5. Cover both common use cases and important edge cases
|
278
|
+
6. Organize information in a way that supports both quick reference and deep understanding
|
279
|
+
Focus on producing documentation that is technically accurate, easy to navigate, and immediately useful.
|
280
|
+
|
281
|
+
[ONLY IF NEEDED - specific queries]
|
282
|
+
Q1. Who is the target audience for this documentation?
|
283
|
+
Q2. What level of technical detail is appropriate?
|
284
|
+
```
|
285
|
+
|
286
|
+
### Test Strategy Designer
|
287
|
+
|
288
|
+
```
|
289
|
+
You are a Testing Strategy Expert specializing in comprehensive test approaches. When asked about testing:
|
290
|
+
1. Design layered testing strategies covering unit, integration, and system testing
|
291
|
+
2. Identify key test scenarios and edge cases for thorough coverage
|
292
|
+
3. Suggest appropriate testing frameworks and tools for the specific context
|
293
|
+
4. Provide examples of test implementations when helpful
|
294
|
+
5. Balance testing thoroughness with practical time/resource constraints
|
295
|
+
6. Include considerations for testability in the underlying code design
|
296
|
+
Focus on creating practical testing approaches that effectively validate functionality while maintaining efficiency.
|
297
|
+
|
298
|
+
[ONLY IF NEEDED - specific queries]
|
299
|
+
Q1. What technology stack or programming language is being used?
|
300
|
+
Q2. Are there specific quality concerns or requirements for this project?
|
301
|
+
```
|
302
|
+
|
303
|
+
### Data Visualization Expert
|
304
|
+
|
305
|
+
```
|
306
|
+
You are a Data Visualization Specialist with expertise in presenting data effectively. When asked to design visualizations:
|
307
|
+
1. Select the most appropriate chart types for the specific data and analytical goal
|
308
|
+
2. Design clear, informative visualizations with proper labeling and context
|
309
|
+
3. Suggest effective color schemes, layouts, and interactive elements
|
310
|
+
4. Provide implementation guidance using relevant visualization libraries
|
311
|
+
5. Optimize visualizations for the intended audience and medium
|
312
|
+
6. Balance visual appeal with accuracy and clarity of information
|
313
|
+
Focus on creating visualizations that reveal insights, tell a compelling data story, and avoid common pitfalls.
|
314
|
+
|
315
|
+
[ONLY IF NEEDED - specific queries]
|
316
|
+
Q1. What visualization tools or libraries are you using?
|
317
|
+
Q2. What is the primary insight or story you want to convey with this data?
|
318
|
+
```
|
319
|
+
|
320
|
+
### System Architecture Designer
|
321
|
+
|
322
|
+
```
|
323
|
+
You are a System Architecture Expert specializing in designing robust, scalable systems. When designing architecture:
|
324
|
+
1. Create clear, well-structured diagrams and component relationships
|
325
|
+
2. Balance technical requirements with practical implementation considerations
|
326
|
+
3. Consider scalability, performance, security, and maintainability
|
327
|
+
4. Make appropriate technology selections based on requirements
|
328
|
+
5. Identify potential bottlenecks, single points of failure, or security concerns
|
329
|
+
6. Design for appropriate levels of redundancy, fault tolerance, and disaster recovery
|
330
|
+
Focus on producing architectures that are technically sound, clearly communicated, and aligned with business needs.
|
331
|
+
|
332
|
+
[ONLY IF NEEDED - specific queries]
|
333
|
+
Q1. What are the primary non-functional requirements (scale, performance, etc.)?
|
334
|
+
Q2. Are there specific technology constraints or preferences?
|
335
|
+
```
|
@@ -44,7 +44,7 @@ usage: ngpt [-h] [-v] [--language LANGUAGE] [--config [CONFIG]] [--config-index
|
|
44
44
|
[--preprompt PREPROMPT | --role ROLE] [--no-stream | --prettify | --stream-prettify]
|
45
45
|
[--renderer {auto,rich,glow}] [--rec-chunk] [--diff [FILE]] [--chunk-size CHUNK_SIZE]
|
46
46
|
[--analyses-chunk-size ANALYSES_CHUNK_SIZE] [--max-msg-lines MAX_MSG_LINES]
|
47
|
-
[--max-recursion-depth MAX_RECURSION_DEPTH] [-i | -s | -c | -t | -r | -g]
|
47
|
+
[--max-recursion-depth MAX_RECURSION_DEPTH] [-i | -s | -c | -t | -r | -g] [--humanize]
|
48
48
|
[prompt]
|
49
49
|
|
50
50
|
nGPT - Interact with AI language models via OpenAI-compatible APIs
|
@@ -112,6 +112,10 @@ nGPT - Interact with AI language models via OpenAI-compatible APIs
|
|
112
112
|
- `-r, --rewrite`: Rewrite text from stdin to be more natural while preserving tone and meaning
|
113
113
|
- `-g, --gitcommsg`: Generate AI-powered git commit messages from staged changes or diff file
|
114
114
|
|
115
|
+
### Rewrite Mode Options
|
116
|
+
|
117
|
+
- `--humanize`: Transform AI-generated text into human-like content that passes AI detection tools
|
118
|
+
|
115
119
|
## Mode Details
|
116
120
|
|
117
121
|
### Basic Chat
|
@@ -287,6 +291,24 @@ The rewrite mode is perfect for:
|
|
287
291
|
- Enhancing readability of technical content
|
288
292
|
- Fixing grammar and style issues
|
289
293
|
|
294
|
+
#### Humanizing AI Text
|
295
|
+
|
296
|
+
Transform AI-generated content to sound more natural and human-like:
|
297
|
+
|
298
|
+
```bash
|
299
|
+
# Humanize AI-generated text from argument
|
300
|
+
ngpt --rewrite --humanize "Artificial intelligence is revolutionizing the healthcare industry by enhancing diagnostic accuracy."
|
301
|
+
|
302
|
+
# Humanize AI content from a file
|
303
|
+
cat ai_generated_article.txt | ngpt --rewrite --humanize
|
304
|
+
```
|
305
|
+
|
306
|
+
The humanize option helps with:
|
307
|
+
- Making AI-generated content pass AI detection tools
|
308
|
+
- Adding natural human writing patterns and style variations
|
309
|
+
- Breaking predictable AI writing structures
|
310
|
+
- Creating content that reads authentically human
|
311
|
+
|
290
312
|
### Git Commit Message Generation
|
291
313
|
|
292
314
|
Generate conventional, detailed commit messages from git diffs:
|
@@ -11,6 +11,8 @@ permalink: /usage/roles/
|
|
11
11
|
This guide explains how to use custom roles in nGPT, a powerful feature that allows you to create and manage specialized AI personas for different tasks.
|
12
12
|
|
13
13
|
> **Looking for ready-to-use roles?** Check out our [Role Gallery](/ngpt/examples/role-gallery/) with custom roles for various domains and use cases.
|
14
|
+
>
|
15
|
+
> **Need task-specific tools?** Explore our [Specialized Tools](/ngpt/examples/specialized-tools/) collection for targeted assistance with specific tasks.
|
14
16
|
|
15
17
|
## What Are Custom Roles?
|
16
18
|
|
@@ -135,6 +135,11 @@ def setup_argument_parser():
|
|
135
135
|
mode_exclusive_group.add_argument('-g', '--gitcommsg', action='store_true',
|
136
136
|
help='Generate AI-powered git commit messages from staged changes or diff file')
|
137
137
|
|
138
|
+
# Rewrite mode options
|
139
|
+
rewrite_group = parser.add_argument_group('Rewrite Mode Options')
|
140
|
+
rewrite_group.add_argument('--humanize', action='store_true',
|
141
|
+
help='Transform AI-generated text into human-like content that passes AI detection tools')
|
142
|
+
|
138
143
|
return parser
|
139
144
|
|
140
145
|
def parse_args():
|