Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub joshuarweaver/cascade-code-general-misc-3 --plugin oraseslabs-orases-claude-code-marketplaceHow this command is triggered — by the user, by Claude, or both
Slash command
/work-summary:setupThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Work Summary Plugin — Setup Guide the user through configuring the work-summary plugin for this project. ## Instructions Walk the user through each setting interactively. Do not dump all options at once. ### Step 1: Check for Existing Settings Look for settings files in priority order: 1. `.claude/work-summary.local.md` (project-local) 2. `.claude/work-summary.md` (project-scoped) 3. `~/.claude/work-summary.md` (user-global) If a settings file is found, show the user their current effective configuration and ask if they want to modify it. If none found, continue to Step 2. ### Step...
/setupInteractively configures MCP servers for Linear, Jira, and GitHub Issues integration, merging settings into project or global config.
/jira-discover-projectDiscovers JIRA project metadata like issue types, components, workflows, patterns; generates defaults and stores context in shared or personal config.
/implementation-summaryGenerates markdown summary of completed feature implementation from state file, specs, reviews, PR/git details, and acceptance criteria into claude_constructor/<issue>/implementation_summary.md.
/close-issueCreates a Pull Request that auto-closes the specified GitHub issue when merged, using isolated git worktrees. Supports --dry-run, --json, --no-worktree, --skip-retro flags.
/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/setupWalks an enterprise admin through configuring the Claude Office add-in to call their own cloud (Vertex, Bedrock, Foundry, or gateway), producing a customized manifest.xml for M365 deployment.
Share bugs, ideas, or general feedback.
Guide the user through configuring the work-summary plugin for this project.
Walk the user through each setting interactively. Do not dump all options at once.
Look for settings files in priority order:
.claude/work-summary.local.md (project-local).claude/work-summary.md (project-scoped)~/.claude/work-summary.md (user-global)If a settings file is found, show the user their current effective configuration and ask if they want to modify it. If none found, continue to Step 2.
Walk through each setting interactively using AskUserQuestion:
Base Branch — "Which branch should changes be compared against?"
autoAtlassian Hostname — "What is your Jira hostname?"
orases.atlassian.netyourcompany.atlassian.net)Post Action — "What should happen after generating a summary?"
askClient Summary — "Include client-friendly summary with QA steps?"
trueTechnical Summary — "Include technical summary with file categories?"
trueLocal Save Path — "Where should local summary copies be saved?"
.claude/work-summariesAuto-detect Ticket — "Auto-detect Jira ticket from branch name?"
trueOnly ask about mcp_server and file_categories if the user indicates they need
non-default values. For most users, the defaults work fine.
Use AskUserQuestion:
"Where should these settings be saved?"
.claude/work-summary.local.md) — Only for you, not committed to git.claude/work-summary.md) — Shared with team via git~/.claude/work-summary.md) — Applies across all your projectsCreate the settings file at the chosen location with YAML frontmatter. Only include settings that differ from defaults to keep the file clean. Use HTML comments to document available settings that were left at defaults.
Refer to ${CLAUDE_PLUGIN_ROOT}/skills/work-summary-generator/templates/settings-template.md for the
complete template and field reference.
Confirm success and suggest:
/work-summary:generate-work-summary to try it out/work-summary:help for more information about capabilities.claude/*.local.md to .gitignore