From slack-forge
Review pending harvest records — approve, reject, edit, or skip each item
How this command is triggered — by the user, by Claude, or both
Slash command
/slack-forge:reviewThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Review Command Present pending harvest records for human review and disposition. ## Instructions ### 1. Query Pending Harvests Query all pending harvest records: Check the `success` field in the JSON response. If `success` is `false`, report the `error` field to the user and stop. Parse the harvests array from the response. If empty: ### 2. Group by Harvest Type Organize pending items into groups: - **Tasks** — harvest_type: "task" - **Knowledge** — harvest_type: "knowledge" - **JIRA Digests** — harvest_type: "jira-digest" Present a summary: ### 3. Review Each Item For each...
Present pending harvest records for human review and disposition.
Query all pending harvest records:
forge harvest query --status pending
Check the success field in the JSON response. If success is false, report the error field to the user and stop.
Parse the harvests array from the response. If empty:
No pending harvest records found.
- To scan channels: /slack-forge:scan
- To check all harvests: forge harvest query
Organize pending items into groups:
Present a summary:
{total} pending harvest records to review:
- {task_count} tasks
- {knowledge_count} knowledge items
- {jira_count} JIRA digests
Reviewing in order: Tasks → Knowledge → JIRA Digests
For each pending item, present the details:
[{harvest_type}] {title}
- Source: #{source_channel} by @{source_author}
- Confidence: {confidence}
- Scanned: {scan_date} ({scan_timeframe})
- File: {filename}
{extracted content preview — first 3-5 lines of body}
Action? (A)pprove / (R)eject / (E)dit / (S)kip
Handle the user's choice:
forge harvest update {filename} --data '{"status": "approved"}'
Check the success field. If success is false, report the error and continue to next item.
forge harvest update {filename} --data '{"status": "rejected"}'
Check the success field. If success is false, report the error and continue to next item.
Prompt the user for changes:
Current title: {title}
New title (or Enter to keep):
Current content preview:
{content}
Updated content (or Enter to keep):
After edits, approve the item with updated fields:
forge harvest update {filename} --data '{"status": "approved", "title": "{new_title}"}'
Check the success field. If success is false, report the error and continue to next item.
Leave the item as pending. Move to the next item without any update.
After all items have been reviewed:
Review complete:
- {approved_count} approved
- {rejected_count} rejected
- {skipped_count} skipped (still pending)
{if approved_count > 0}
Approved items are ready for promotion. Run /slack-forge:promote to push to tasks-forge and forge-memory.
{/if}
forge harvest update CLInpx claudepluginhub jeremybrice/the-forge --plugin slack-forge/review-queueTriages pending human-review items from the SoloFlow queue — resolves cruft, walks Decisions/Actions/Testing/Deferred Visual buckets, and refines found issues into backlog tasks.
/reviewReviews pending self-care reports in ./.self-care/reports/, walking through findings for each, categorizing them, and updating status. Optional count limits reports reviewed.
/phase4-queueChecks memory-palace knowledge queue for pending items, reports status table, prompts for promote/archive/defer decisions on old items, and executes file moves/updates.
/triageTriage open HUMAN.md feedback entries, moving each to adopted, obsolete, or merged based on linked PRs and friction logs. Also supports re-reading adopted items for obsolescence.
/approveManages Jira approval workflows: request PR/deploy/release/issue, approve/reject with comments, status/list pending/history, configure.
/sugar-reviewReviews pending Sugar tasks interactively: lists by priority, offers view/update/edit/execute/remove actions. Supports --priority N, --type TYPE, --limit N filters.