Quick Start
Generate a PR description for your current branch:How It Works
Analyze Branch
DevDaily examines your current branch, comparing it to the base branch to identify all commits and changes.
Extract Context
Collects ticket IDs from branch names and commit messages, fetches ticket details, and analyzes code diffs.
Apply Template
If a PR template exists (
.github/PULL_REQUEST_TEMPLATE.md), it structures the content accordingly.AI Generation
Uses GitHub Copilot CLI to generate a comprehensive description following your team’s guidelines.
Command Options
Basic Options
| Option | Description | Default |
|---|---|---|
-b, --base <branch> | Base branch to compare against | Auto-detected or main |
-c, --create | Create PR on GitHub immediately | false |
-d, --draft | Create as draft PR | false |
-p, --preview | Show preview before creating | false |
Context Control
| Option | Description |
|---|---|
-t, --ticket <id> | Include specific ticket/issue for context |
--no-tickets | Skip fetching ticket context |
--no-template | Ignore PR template, use default format |
--no-diff | Skip including diff context in AI prompt |
--no-prompt-file | Ignore custom PR prompt file |
- With Tickets
- With Template
- With Diff
Interactive Mode
| Option | Description |
|---|---|
-i, --interactive | Interactive mode for labels, reviewers, assignees |
Interactive mode fetches repository metadata and allows you to select:
- Labels to apply to the PR
- Reviewers to request
- Assignees for the PR
Clipboard and Journal
| Option | Description |
|---|---|
--no-copy | Don’t copy to clipboard |
--no-journal | Skip auto-saving snapshot to journal |
--debug | Show debug information (prompts, raw AI input) |
PR Templates
DevDaily automatically detects and uses PR templates from your repository:Supported Template Locations
.github/PULL_REQUEST_TEMPLATE.md.github/pull_request_template.mdPULL_REQUEST_TEMPLATE.mddocs/PULL_REQUEST_TEMPLATE.md
Template Sections
The AI recognizes common template sections and fills them appropriately:- Description: Summary of changes
- Type: Feature, bugfix, refactor, etc.
- Impact: Affected areas and potential risks
- Testing: How changes were tested
- Breaking Changes: Any breaking changes introduced
- Additional Info: Context, screenshots, notes
Custom PR Guidelines
You can provide team-specific PR writing guidelines:Create a PR Prompt File
Add.devdaily/pr-prompt.md to your repository:
What Gets Analyzed
Branch Information
- Current branch name
- Base branch for comparison
- Branch creation point
Commits
- All commit messages on the branch
- Commit hashes and authors
- Commit timestamps
Code Changes
- Files changed
- Diff statistics (insertions/deletions)
- Code diff content (configurable limit)
Tickets & Issues
- Ticket IDs extracted from:
- Branch name (e.g.,
feature/PROJ-123-login) - Commit messages
- Manual
--ticketflag
- Branch name (e.g.,
- Ticket details from your PM tool:
- Title and description
- Status and priority
- Type (bug, feature, task)
PR Title Generation
The AI generates PR titles following conventional commit style:feat: Add user authenticationfix: Resolve login redirect issuerefactor: Simplify auth flowdocs: Update API documentation
PR Type Detection
PR Type Detection
DevDaily analyzes commit messages to determine PR type:
- feature: New features (
feat:,feature:) - fix: Bug fixes (
fix:,bugfix:) - refactor: Code refactoring (
refactor:) - docs: Documentation (
docs:) - test: Tests (
test:) - chore: Maintenance (
chore:)
Interactive Actions
After generating a PR description, you can:- Copy to clipboard - For manual PR creation
- Create PR on GitHub - Direct GitHub integration
- Create draft PR - Mark as work-in-progress
- Preview in browser - Open GitHub compare view
- Configure labels & reviewers - Interactive metadata selection
Example Workflows
Basic PR Creation
Draft PR with Preview
Interactive with Labels
Custom Base Branch
Quick Copy to Clipboard
Output Preview
When using--preview or --interactive, you’ll see:
GitHub Integration
Requires
gh CLI authenticated with GitHubCreate PR Directly
- Push your branch to remote if needed
- Create the PR on GitHub
- Apply labels if selected
- Request reviewers if selected
- Assign the PR if specified
- Return the PR URL
Preview in Browser
Open GitHub’s compare view without creating a PR:Configuration
Customize PR generation in.devdaily.json:
Configuration Options
| Option | Description | Default |
|---|---|---|
pr.defaultBase | Default base branch | "main" |
pr.includeDiff | Include diff in AI prompt | true |
pr.maxDiffLines | Max diff lines to include | 200 |
Troubleshooting
Cannot create PR from main branch
Cannot create PR from main branch
You cannot create a PR from the base branch itself.
No commits on this branch
No commits on this branch
Ensure you have commits on your branch:If empty, make some commits first.
Copilot CLI not found
Copilot CLI not found
Install GitHub Copilot CLI:
Failed to create PR
Failed to create PR
Ensure
gh CLI is authenticated:Related Commands
devdaily standup- Generate standup notesdevdaily week- Generate weekly summariesdevdaily context- Recover work context