workflow-lifecyclelisted

Repository governance workflow for f5-sales-demo — issue creation, branch naming, PR workflow, CI polling, post-merge monitoring, verification, and task completion criteria. Use when the user says "lets sync to github", "sync to github", "sync to gh", "commit", "push", "create a pr", "open a pr", "merge", "check ci", "poll ci", "create an issue", "create a branch", "start a new task", "land these changes", "ship it", "submit for review", "monitor ci", "check the build", "run pre-commit", "lint gate", "push changes", "open a pull request", "squash merge", or "check rate limit". Also activates when any code-change workflow requires Git operations, when the main session has finished editing files and needs to commit, or when encountering HTTP 403/429 from the GitHub API. Does NOT handle code editing, file creation, file modification, test writing, debugging, or any non-Git operation. Does NOT fix lint or CI failures — it reports them and stops. Delegates mechanical Git lifecycle tasks to the github:github-ops su
f5-sales-demo/marketplace · ★ 0 · Code & Development · score 71

Install: claude install-skill f5-sales-demo/marketplace

**Canonical skill URI**: `skill://github:workflow-lifecycle` # Repository Workflow Lifecycle <role> You manage the lifecycle delegation protocol. You delegate mechanical Git and GitHub operations (issue creation, feature branching, staging, pre-commit linting, PR creation, CI monitoring, post-merge teardown) to the specialized `github-ops` agent. </role> <delegation_protocol> ## Delegation Procedure Upon completing file modifications in the main session, delegate Git lifecycle execution to the `github-ops` agent: ```text Agent( subagent_type="github:github-ops", mode="bypassPermissions", prompt="<type>: <description>\n\nFiles:\n- <file-list>\n\nWhy: <motivation>" ) ``` *Rationale for bypassPermissions*: The `github-ops` agent performs a continuous multi-step Git lifecycle (issue creation → branch creation → staging -> commit -> pre-commit -> push -> PR creation -> CI polling -> merge). Running in `bypassPermissions` ensures uninterrupted execution through completion. Optional prompt fields: - `Issue: #<number>` — provide existing issue ID (bypasses issue creation step). - `Branch: <branch-name>` — provide existing feature branch name (bypasses branch creation step). </delegation_protocol> <verification> ## Issue Linkage Verification When `github-ops` completes execution, confirm the status report includes a valid linked issue reference (`#<number>`). If additional verification is desired, validate the PR body reference: ```bash gh pr view <PR-NUMBER> --js