Validate quality with multi-agent review, auto-fix issues, generate organized commits, and create PRs with rich context. Use after completing features to ensure quality gates pass and ship confidently.
Automates shipping code: validates quality, auto-fixes issues, generates organized commits, and creates PRs with rich context. Use after completing features to ensure quality gates pass and ship confidently.
/plugin marketplace add jeanluciano/quaestor/plugin install quaestor@quaestorThis skill is limited to using the following tools:
AGENTS.mdCOMMITS.mdMODES.mdPR.mdWORKFLOW.mdI help you ship code confidently: validate quality, fix issues, generate commits, review with agents, and create pull requests.
Review & validate:
Create pull request:
Generate commits:
Most common: Just completed work and want to ship it
"Review and ship this feature"
I'll automatically:
Just need PR: Already validated and committed
"Create a PR for spec-feature-001"
I'll skip validation and just create the PR.
I detect what you need and adapt:
When: "Review my changes", "Ship this" Steps: Validate → Fix → Commit → Review → PR
Load: @WORKFLOW.md for complete 5-phase process
When: "Quick review", small changes Steps: Basic validation → Fast commits → Simple PR
Load: @MODES.md for quick mode details
When: "Create a PR", "Make pull request" Steps: Generate PR description from spec/commits → Submit
Load: @PR.md for PR creation details
When: "Generate commits", "Organize my commits" Steps: Analyze changes → Create atomic commits
Load: @COMMITS.md for commit strategies
When: "Validate my code", "Check quality" Steps: Run quality gates → Report results
Load: @WORKFLOW.md Phase 1
When: "Analyze code quality", "Review for issues" Steps: Multi-agent review → Detailed report
Load: @AGENTS.md for review strategies
Don't load all files! Only load what's needed for your workflow:
User Intent Detection:
"review my changes" → Load @WORKFLOW.md (full 5-phase)
"create a PR" → Load @PR.md (PR creation only)
"generate commits" → Load @COMMITS.md (commit organization)
"quick review" → Load @MODES.md (mode selection)
"validate code" → Load @WORKFLOW.md Phase 1 (validation)
When running full review:
See @WORKFLOW.md Phase 1 for validation details
See @AGENTS.md for fix strategies
See @COMMITS.md for commit generation
See @AGENTS.md for review coordination
See @PR.md for PR creation
✅ Language-specific validation (Python, Rust, JS, Go) ✅ Multi-domain checks (code, security, tests, docs) ✅ Automatic fixing of common issues ✅ Clear pass/fail reporting
✅ Groups related changes by module ✅ Atomic commits (one logical change) ✅ Conventional commit format ✅ Links to specifications
✅ Parallel agent execution ✅ Domain-specific expertise ✅ Actionable suggestions ✅ Required fix identification
✅ Spec-driven descriptions ✅ Quality metrics included ✅ Test coverage reported ✅ Links to specifications ✅ Review insights attached
User: "Review and ship spec-feature-001"
Me:
1. Validate: Run tests, linting, security scan
2. Fix: Auto-fix formatting, delegate complex issues
3. Commit: Generate organized commits
4. Review: Multi-agent code review
5. PR: Create comprehensive pull request
User: "Create PR for spec-feature-001"
Me:
1. Find completed spec
2. Generate PR description
3. Create GitHub PR
4. Report URL
User: "Validate my code"
Me:
1. Run all quality gates
2. Report results (✅ or ❌)
3. If issues: List them with fix suggestions
4. Ask: "Fix issues and ship?" or "Just report?"
Total if all loaded: 5609 lines Typical usage: 200-1500 lines (only what's needed)
Full workflow complete when:
PR-only complete when:
I handle the entire "code is done, make it shippable" workflow. From validation to PR creation, I ensure quality and create comprehensive documentation for reviewers.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.