publishing-stories | story-driven | ClaudePluginHub

Skill

Community

publishing-stories

From story-driven

0

Description

Guides commit, push, and draft PR creation for stories. Use when ready to commit changes, pushing to remote, or creating a pull request for review.

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Skill Content

Committing and Publishing

Timing Flexibility

Acceptance testing can occur at different points depending on team workflow:

Workflow	When to Accept
Pre-commit	Developer verification → PO accepts → Commit
Pre-push	Commit locally → PO accepts → Push
Post-PR	Commit → Push → Draft PR → PO accepts → Ready for review

Choose based on:

How quickly PO can review
Whether you need a deployed preview
Team conventions

Pre-Commit Checklist

Before Commit:
- [ ] Developer verification complete
- [ ] All tests pass
- [ ] Linting passes
- [ ] Story log updated with completed work

Commit Message

Use Conventional Commits format:

<type>(<scope>): <summary>

<body explaining why this change is necessary>

Types: feat, fix, refactor, test, docs, chore

Example:

feat(sync): implement workspace Git initialization

Enable users to sync their notes to GitHub by
initializing the workspace as a Git repository.

Guidelines:

Title: what changed and why it matters (imperative mood)
Body: why this change is necessary in broader context
Avoid restating what the diff shows

Push

git push -u origin <branch-name>

Draft Pull Request

For post-PR acceptance workflow:

gh pr create --draft --title "<title>" --body "$(cat <<'EOF'
## Summary
- [Key change 1]
- [Key change 2]

## Story
[Link to story log if applicable]

## Test Plan
- [How to verify this works]

**Status: Awaiting acceptance testing**
EOF
)"

Mark as ready after acceptance:

gh pr ready

Post-Acceptance

After product owner accepts:

Update story log status to "Accepted"
If using draft PR workflow, mark PR as ready
Request code review if required

Links

GitHub Stats

0 forks

Updated 2 hours ago

Related Skills

Agent Development

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.

From plugin-dev

Command Development

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.

From plugin-dev

Hook Development

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.

From plugin-dev