Skip to content

chore(release): promote next to production (2026-03-02)#415

Open
hello-happy-puppy wants to merge 4 commits intomainfrom
release/next-to-main-20260302-171417
Open

chore(release): promote next to production (2026-03-02)#415
hello-happy-puppy wants to merge 4 commits intomainfrom
release/next-to-main-20260302-171417

Conversation

@hello-happy-puppy
Copy link
Collaborator

@hello-happy-puppy hello-happy-puppy commented Mar 2, 2026

Production Deployment

This PR promotes the next branch to main for production release.

Commits included (4):

6f176cf fix(review): use shallow checkout with targeted merge base fetch (#414)
6e40ea8 feat(development-pr-workflow): rewrite resolve-pr-issues as orchestration pipeline (#410)
ea2d01d feat(development-productivity): add generate-document skill using pandoc (#413)
0e3a076 chore(sync): [skip ci] sync next with main

Merge Strategy

Using merge commit to preserve full commit history for changelog generation.

Temporary Branch

This PR is created from a temporary branch release/next-to-main-20260302-171417 that will be deleted after merge.


This PR was automatically created by the Update Production workflow.


Changes Summary

✨ Features (2)

  • Rewrite resolve-pr-issues as orchestration pipeline for improved development workflow
  • Add generate-document skill using pandoc for document generation capabilities

🐛 Bug Fixes (1)

  • Use shallow checkout with targeted merge base fetch in code review workflow

📝 Documentation (1)

  • Update skill documentation and PR resolution guides with comprehensive instructions

Full Commit List

6f176cf fix(review): use shallow checkout with targeted merge base fetch (#414)
6e40ea8 feat(development-pr-workflow): rewrite resolve-pr-issues as orchestration pipeline (#410)
ea2d01d feat(development-productivity): add generate-document skill using pandoc (#413)
0e3a076 chore(sync): [skip ci] sync next with main

hello-happy-puppy and others added 4 commits February 23, 2026 22:45
…doc (#413)

* feat(development-productivity): add generate-document skill using pandoc

Adds a new skill for generating professional documents in multiple formats
(PDF, DOCX, HTML, ODT, EPUB, RTF) using pandoc instead of fpdf2.

Key improvements over PR #412's approach:
- Uses pandoc for universal document conversion
- Supports 7 output formats (PDF, DOCX, HTML, ODT, EPUB, RTF, TXT)
- Full unicode support (no character restrictions)
- Markdown-based input (Claude's native strength)
- Professional formatting with customizable templates
- Better maintainability through standard tooling

Includes templates for security reports, code reviews, and research summaries.

Version bump: 2.0.1 -> 2.1.0 (minor: new feature)

https://claude.ai/code/session_01NZ72YNouJuHYoTGLziyubM

* fix(development-productivity): scope rm permission and use cwd for output path

Address PR review feedback:
- Scope Bash(rm:*) to Bash(rm:/tmp/document_*:*) for tighter permissions
- Add Bash(mkdir:*) to allowed-tools for directory creation
- Default output path to current working directory instead of ~/dev/
- Add instruction to mkdir -p custom output directories before pandoc

* refactor(development-productivity): apply skill best practices to generate-document

Apply progressive disclosure pattern to generate-document skill:
- Move content-type templates to references/templates.md
- Move troubleshooting to references/troubleshooting.md
- Add missing name field to YAML frontmatter
- Remove redundant content Claude already knows (format table,
  install commands, basic markdown/pandoc guidance)
- Fix nested fenced code block structure

Also fix markdownlint config to exclude .trunk/ directory, which
contains symlinked third-party plugin cache files that fail linting.

SKILL.md reduced from 373 to ~174 lines while preserving all functionality.

---------

Co-authored-by: Claude <[email protected]>
…tion pipeline (#410)

* feat(development-pr-workflow): rewrite resolve-pr-issues as orchestration pipeline

Redesign the resolve-pr-issues skill from a loose reference guide into a
structured 7-phase orchestration workflow that:

- Fetches all PR feedback: inline comments, review bodies (via gh api),
  and CI status in parallel
- Normalizes feedback into a unified item list with blocking classification,
  resolved/outdated detection, and CI bot deduplication
- Triages each item (ACTION_REQUIRED → subagent, RESPOND_ONLY → post reply,
  NO_ACTION → skip) using an explicit decision tree
- Dispatches comment-resolver-agent subagents per file group for code changes
- Posts substantive replies for items that don't need code changes
- Detects project tooling before running verification
- Asks user before committing

Also adds:
- New comment-resolver-agent for per-file comment resolution
- Updated pr-guide.md with triage framework, reply protocol, and CI handling
- Plugin version bump 2.0.1 → 2.1.0

* fix(development-pr-workflow): address PR review comments

- Add cross-agent file conflict detection in Phase 5 — orchestrator
  compares modified file lists from parallel agents and re-runs
  sequentially if overlaps detected
- Fix verification --base flag to use PR base branch (origin/next)
  instead of HEAD to match CI behavior
- Fix CI bot dedup to preserve CI failures when inline bot comment
  is stale/resolved
- Update comment-resolver-agent to emphasize reporting all modified
  files for conflict detection

* docs(development-pr-workflow): add comment-resolver-agent to README

The docs-check bot flagged that the new comment-resolver-agent was
missing from the README Agents table despite being in plugin.json
and CLAUDE.md.

* fix(development-pr-workflow): apply review-fix-loop improvements to resolve-pr-issues

- Reorder agents table in README to match plugin.json order
- Expand MCP tool prefixes in SKILL.md allowed-tools (support both plugin namespaces)
- Add merged/closed PR state warning to Phase 0 validation
- Clarify changed files list purpose in Phase 1 gather table
- Differentiate error handling tiers (inline stop-and-surface vs CI continue-with-note)
- Add "security"/"vulnerability" blocking overrides and "minor"/"nice to have" non-blocking
- Add rule 6 for ambiguous bug concerns (RESPOND_ONLY with user-review flag)
- Batch unlocated review body items (up to 3 per agent) and cap CI failure agents at 3
- Fix gh api reply commands to use mktemp + -F body=@file to prevent shell injection
- Align pr-guide.md dispatch table and decision tree with SKILL.md
- Remove redundant local verification section from pr-guide.md (pointer in SKILL.md)
* chore(sync): [skip ci] sync next with main

* fix(review): use faster checkout

---------

Co-authored-by: Uniswap Labs Service Account <[email protected]>
@hello-happy-puppy hello-happy-puppy requested a review from a team as a code owner March 2, 2026 17:14
@vercel
Copy link

vercel bot commented Mar 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
ai-toolkit-claude-review-bot-unleashed Error Error Mar 2, 2026 5:14pm
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
ai-toolkit-slack-oauth-backend Ignored Ignored Preview Mar 2, 2026 5:14pm
ai-toolkit-slack-oauth-backend (staging) Ignored Ignored Mar 2, 2026 5:14pm

Request Review

@github-actions github-actions bot requested a review from wkoutre March 2, 2026 17:15
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.

3 participants