PR Workflow

Ship features from commit to merged pull request. This workflow covers crafting commit messages, preparing PRs, reviewing, and resolving feedback threads.

When to Use This

• You have code ready to commit and want a clean conventional commit message.
• You are ready to open a pull request with a well-written description.
• You need to review someone else's pull request.
• You have review feedback to address and threads to resolve.
• You want to work on a GitHub/GitLab issue from start to finish.

What You'll Use

Walkthrough

Scenario: Ship a feature from commit to merged PR.

Step 1: Commit with Conventional Messages

Stage your changes and run /commit-msg:

git add src/

"Generate a commit message for these changes."

The commit-messages skill analyzes the diff and drafts a conventional commit message following the format type(scope): description. It also runs slop detection, removing AI-generated filler language like "robust", "elegant", or "leverage".

Step 2: Prepare the Pull Request

Run /prepare-pr when all commits are ready:

"Prepare a PR for this feature branch."

The pr-agent generates:

• Title — Conventional commit format, suitable for squash merge
• Description — Explains the why of the change, not just the what
• Self-review checklist — Items to verify before requesting review
• Labels and reviewers — Suggested based on the changed files

Step 3: Review a PR

When reviewing someone else's PR, run /pr-review:

"Review PR #42."

The pr-review skill performs comprehensive analysis:

• Scope validation — Does the PR do one thing?
• Code quality — Bugs, style, architecture concerns
• Test coverage — Are changes tested?
• Breaking changes — Does this affect existing behavior?

Step 4: Address Feedback

After receiving review comments, use /fix-pr to address issues and /resolve-threads to close resolved conversations.

Issue-Driven Workflow

For issue-driven development, start with /do-issue:

"/do-issue #15"

Sanctum follows a progressive workflow:

1. Analyze the issue requirements
2. Specify the approach
3. Plan the implementation
4. Implement the solution
5. Commit and PR automatically

Quick Reference

Tips

• /commit-msg enforces Ontopix git conventions automatically: conventional commits, imperative mood, no trailing period.
• The PR title becomes the squash commit message on master. Make it descriptive.
• /do-issue is the most powerful sanctum workflow — it handles the entire flow from issue to merged PR.
• Works with GitHub, GitLab, and Bitbucket. Platform detection is automatic via leyline's git-platform skill.

See Also

• sanctum plugin — Full plugin documentation
• Code Review workflow — Previous step: review the code
• Contributing — PR guidelines for this repository