Skip to content

Enhance prompting documentation with comprehensive guidance #1105

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

codegen-sh[bot]
Copy link
Contributor

@codegen-sh codegen-sh bot commented May 25, 2025

Overview

This PR significantly enhances the prompting documentation to provide more comprehensive, practical guidance for users working with Codegen across different platforms and use cases.

Key Improvements

🎯 Platform-Specific Guidance

  • Slack Integration: Tips for threading, repo tagging, and status updates
  • Linear Integration: Issue management, sub-task breakdown, and acceptance criteria
  • GitHub Integration: PR reviews, file references, and review criteria

📋 Common Task Types

Added detailed examples for:

  • Code reviews with security and performance focus
  • Bug fixing with investigation and monitoring
  • Feature development with real-time systems
  • Refactoring with testability improvements

🚀 Advanced Techniques

  • Context Provision: How to effectively share codebase information
  • Iterative Prompting: Building on previous work and follow-ups
  • Complex Dependencies: Coordinating changes across multiple services

🔧 Troubleshooting Section

Common issues and solutions:

  • "I don't have enough context" → Provide file paths and patterns upfront
  • "Changes broke functionality" → Specify regression testing requirements
  • "Doesn't match patterns" → Reference specific examples
  • "Task too large" → Break down into smaller, specific tasks

💡 Enhanced Best Practices

  • Visual card layout for key principles
  • Emphasis on Codegen's codebase understanding capabilities
  • Links to related documentation sections

What's Preserved

  • Maintained the excellent existing structure and core 5-element framework
  • Kept all original examples that work well
  • Preserved the accessible, scannable format

Files Modified

The documentation now provides practical, actionable guidance that helps users get better results from Codegen across all supported platforms and use cases.


💻 View my workAbout Codegen

- Add platform-specific guidance for Slack, Linear, and GitHub
- Include common task type examples (code review, bug fixing, feature dev, refactoring)
- Add advanced techniques section with context provision and iterative prompting
- Include troubleshooting section for common issues
- Add best practices cards and getting help section
- Expand examples to be more realistic and diverse
- Maintain existing structure while significantly expanding practical value
Copy link

codecov bot commented May 25, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor Author

codegen-sh bot commented May 25, 2025

I see a check failed - I'm on it! 🫡

💻 View my work

- Fix numbered list formatting (use 1. for all items)
- Remove trailing whitespace
- Add proper blank lines before headers
- Ensure file ends with newline
Copy link
Contributor Author

codegen-sh bot commented May 25, 2025

✅ Fixed the failing check suite for PR #1105!

The issue was with formatting in the prompting.mdx file. I've addressed:

  • Numbered list formatting (changed to use "1." for all items)
  • Removed trailing whitespace
  • Added proper spacing before headers
  • Ensured file ends with newline

The fix has been pushed to the PR branch in this commit. The formatting issues were being caught by the pre-commit linting tools.

💻 View my work • React 👍 or 👎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants