shannon/.claude/commands/pr.md at main

mirror of https://github.com/KeygraphHQ/shannon.git synced 2026-02-12 09:12:50 +00:00

Files

Arjun Malleswaran ae4c4ed402 fix: add file_path parameter to save_deliverable for large reports (#123 )

* fix: add file_path parameter to save_deliverable for large reports

Large deliverable reports can exceed output token limits when passed as
inline content. This change allows agents to write reports to disk first
and pass a file_path instead.

Changes:
- Add file_path parameter to save_deliverable MCP tool with path
  traversal protection
- Pass CLAUDE_CODE_MAX_OUTPUT_TOKENS env var to SDK subprocesses
- Fix false positive error detection by extracting only text content
  (not tool_use JSON) when checking for API errors
- Update all prompts to instruct agents to use file_path for large
  reports and stop immediately after completion

* docs: simplify and condense CLAUDE.md

Reduce verbosity while preserving all essential information for AI
assistance. Makes the documentation more scannable and focused.

* feat: add issue number detection to pr command

The /pr command now automatically detects issue numbers from:
1. Explicit arguments (e.g., /pr 123 or /pr 123,456)
2. Branch name patterns (e.g., fix/123-bug, issue-456-feature)

Adds "Closes #X" lines to PR body to auto-close issues on merge.

* chore: remove CLAUDE_CODE_MAX_OUTPUT_TOKENS env var handling

No longer needed with the new Claude Agent SDK version.

* fix: restore max_output_tokens error handling

2026-02-11 13:40:49 -08:00

1.9 KiB

Raw Permalink Blame History

description

description
Create a PR to main branch using conventional commit style for the title

Create a pull request from the current branch to the main branch.

Arguments

The user may provide issue numbers that this PR fixes: $ARGUMENTS

If provided (e.g., 123 or 123,456), use these issue numbers
If not provided, check the branch name for issue numbers (e.g., fix/123-bug or issue-456-feature → extract 123 or 456)
If no issues are found, omit the "Closes" section

Steps

First, analyze the current branch to understand what changes have been made:

Run git log --oneline -10 to see recent commit history and understand commit style
Run git log main..HEAD --oneline to see all commits on this branch that will be included in the PR
Run git diff main...HEAD --stat to see a summary of file changes
Run git branch --show-current to get the branch name for issue detection (if no explicit issues provided)

Then generate a PR title that:

Follows conventional commit format (e.g., fix:, feat:, chore:, refactor:)
Is concise and accurately describes the changes
Matches the style of recent commits in the repository

Generate a PR body with:

A ## Summary section with 1-3 bullet points describing the changes
A Closes #X line for each issue number (if any were provided or detected from branch name)

Finally, create the PR using the gh CLI:

gh pr create --base main --title "<generated title>" --body "$(cat <<'EOF'
## Summary
<bullet points>

Closes #<issue1>
Closes #<issue2>
EOF
)"

Note: Omit the "Closes" lines entirely if no issues are associated with this PR.

IMPORTANT:

Do NOT include any Claude Code attribution in the PR
Keep the summary concise (1-3 bullet points maximum)
Use the conventional commit prefix that best matches the changes (fix, feat, chore, refactor, docs, etc.)
The Closes #X syntax will automatically close the referenced issues when the PR is merged

1.9 KiB Raw Permalink Blame History

Arguments

Steps

1.9 KiB

Raw Permalink Blame History