create_github_prompt
Create new prompts and save them directly to a GitHub repository, with built-in duplicate detection to avoid redundancy.
Instructions
✨ Create New Prompt: Create a new prompt and save it directly to the GitHub repository. 🎯 WORKFLOW: Always use search_prompts first to check if a similar prompt already exists. Only create new prompts when needed to avoid duplicates.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Unique identifier for the prompt. Use lowercase with underscores. Examples: "code_review_assistant", "api_documentation_generator", "database_design_helper" | |
| tags | No | 2-5 relevant tags for discoverability. Examples: ["code-review", "github", "quality"], ["api", "documentation", "openapi"], ["database", "sql", "design"] | |
| title | Yes | Human-readable title that clearly explains the prompt's purpose. Examples: "Code Review Assistant for Pull Requests", "API Documentation Generator", "Database Schema Designer" | |
| author | No | Author name or handle | |
| content | Yes | The actual prompt template content. Use {{variable_name}} for dynamic placeholders. Include clear instructions and examples in the prompt. | |
| category | No | Choose from existing categories: "development", "content-creation", "business", "ai-prompts", "devops", "documentation", "project-management". Use list_prompt_categories to see all options. | |
| arguments | No | Template arguments for dynamic content | |
| difficulty | No | Complexity level of the prompt | |
| description | Yes | Clear, concise description of what the prompt does and when to use it. Include the main benefits and use cases. | |
| commitMessage | No | Git commit message. Defaults to "Add prompt: [name]" |