Auto-load workflow settings when working in a project directory
Automatically loads workflow configuration from `.claude/workflow.json` when other plugins need Git, Jira, Notion, or Confluence settings. Used implicitly by integration plugins to apply project-specific workflows for branching, commits, and issue tracking.
/plugin marketplace add minukHwang/claude-plugins/plugin install workflow@minukHwang-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Automatically load and apply workflow settings when working in a project.
This skill should be used implicitly by other plugins (git, jira, confluence, notion) when they need to read workflow configuration.
cat .claude/workflow.json 2>/dev/null
If file exists, parse and extract:
Git Settings:
git.strategy - Branching strategy (github-flow, git-flow, trunk-based)git.branches.main - Main branch namegit.branches.develop - Develop branch name (for git-flow)git.merge.method - Merge method (squash, merge, rebase)git.pr.defaultTarget - Default PR target branchJira Settings:
jira.enabled - Whether Jira integration is activejira.cloudId - Atlassian cloud IDjira.projectKey - Current project keyjira.includeInBranch - Include issue key in branch namesjira.includeInCommit - Include issue key in commit messagesNotion Settings:
notion.enabled - Whether Notion integration is activenotion.databases.todo.id - TODO database IDnotion.databases.til.id - TIL database IDnotion.databases.blog.id - BLOG database IDConfluence Settings:
confluence.enabled - Whether Confluence sync is activeconfluence.spaceKey - Confluence space key# In git:branch, git:commit, git:pr
## Step 0: Load Workflow Context
cat .claude/workflow.json 2>/dev/null
If jira.enabled && jira.includeInBranch:
- Offer to link Jira issue to branch
- Include issue key in branch name
If jira.enabled && jira.includeInCommit:
- Extract issue key from branch name
- Append [ISSUE-KEY] to commit message
# In jira:start, jira:create, jira:done
## Step 0: Load Workflow Context
cat .claude/workflow.json 2>/dev/null
Use jira.cloudId for API calls
Use jira.projectKey for issue queries
Use notion.databases.todo.id for Notion sync
# In confluence:sync
## Step 0: Load Workflow Context
cat .claude/workflow.json 2>/dev/null
If confluence.enabled:
- Sync files to Confluence
- Use confluence.spaceKey for page creation
# In notion:til, notion:blog
## Step 0: Load Workflow Context
cat .claude/workflow.json 2>/dev/null
If notion.enabled:
- Use notion.databases.til.id for TIL
- Use notion.databases.blog.id for BLOG
When .claude/workflow.json does not exist:
/workflow:initExample message:
ℹ Workflow not configured. Run /workflow:init to set up Jira and Git integration.
When workflow.json exists but specific settings are missing:
| Setting | Default |
|---|---|
| git.strategy | github-flow |
| git.branches.main | main |
| git.merge.method | squash |
| jira.enabled | false |
| jira.includeInBranch | true |
| jira.includeInCommit | true |
| notion.enabled | false |
| confluence.enabled | false |
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.