aiw-githublisted

Rules for every GitHub and git history action during a task: starting work on an issue, switching branches, rebasing, committing, pushing, opening a pull request, post-merge cleanup, and handling parent and sub-issue hierarchies. Use this skill whenever the agent is about to read a GitHub issue at task start, create or switch to a branch, run a rebase, create a commit, push to remote, open a pull request, or run post-merge cleanup, even if the user does not name the action explicitly. Also use when the agent encounters a parent issue with sub-issues, when a deterministic policy hook blocks a git action, or when the agent suspects new commits have landed on the target branch since the last rebase. The skill exists to keep GitHub actions traceable to an issue, taken after the done gate, safe against silent working-tree loss during branch operations, and short of the one action that stays the human's: the merge.
philippe-ths/ai-coding-workflow · ★ 0 · AI & Automation · score 66

Install: claude install-skill philippe-ths/ai-coding-workflow

# GitHub Workflow ## Why this skill exists GitHub actions touch shared state. Each one becomes visible to others the moment it lands. Branch operations can silently lose untracked files. Issues anchor scope; without one, work drifts and commits lose traceability. This skill keeps each action anchored to an issue, taken only after the done gate, and safe against working-tree surprises. The merge is the human's, and the policy layer blocks the agent from it deterministically. ## Starting work on an issue - Confirm the GitHub issue number before any other action. - Read the issue body and the issue comments. Comments often carry scope changes, clarifications, and constraints not in the original body. - If the issue has sub-issues, treat the parent as broader context. Stop and ask the human which sub-issue to work on. Do not implement the full parent scope. - If the issue is a sub-issue, read the direct parent issue and its comments for context. Do not read further up the hierarchy. - When completing a sub-issue, check whether it is the last open sub-issue under the parent. If it is, flag this to the human. ## Branch protection and naming - Never work directly on `main` or `master`. - Create or switch to an issue-scoped branch before editing files or making commits. - Use the format `type/short-description` for branch names. ## Rebasing onto the target branch - Rebase the issue branch onto the target branch before starting implementation. - Rebase again before any remote