Complete development lifecycle for GitHub/local issues - branch, implement, test, PR, merge with quality gates
/plugin marketplace add bryonjacob/aug/plugin install aug-dev@augThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Complete workflow: branch → code → tests → PR → merge. Works for GitHub and local issues (ISSUES.LOCAL/).
Core principle: One issue at a time, full lifecycle before next.
Standard Interface: aug-just/justfile-interface (Level 0+1)
just test-watch # Continuous testing
just check-all # Quality gate before merge
# 1. Get issue
gh issue view [NUMBER] # GitHub
cat ISSUES.LOCAL/LOCAL###-Title.md # Local
# 2. Branch (if not in worktree)
git checkout -b [ISSUE_ID]-description
# 3. Implement with TDD
just test-watch
# 4. Quality gate
just check-all
# 5. PR (GitHub only)
gh pr create --draft
gh pr ready
# 6. Merge
gh pr merge --squash --delete-branch # GitHub
git merge --squash BRANCH # Local
Check:
git rev-parse --git-dir # .git = main, worktrees/name = worktree
In worktree: Already on feature branch, work normally
Not in worktree: git checkout -b [ISSUE_ID]-description
42-add-user-authLOCAL001-fix-parser1. Read acceptance criteria
2. TDD cycle
3. Commit messages
git commit -m "feat: specific change
Refs #42"
4. Draft PR early (GitHub)
gh pr create --draft --title "feat: description" --body "Closes #42"
just check-all passesGitHub:
gh pr ready
gh pr merge --squash --delete-branch
Local:
sed -i '' 's/^status: ready$/status: closed/' ISSUES.LOCAL/LOCAL###-Title.md
git checkout main
git merge --squash BRANCH
git commit -m "feat: description
Closes LOCAL###"
git branch -d BRANCH
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 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 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.