メニュー
Use when working in the a11y-cop repository and need to perform git or GitHub operations. This is THE authoritative guidance for proper git/gh interaction in this repo, including branching, commits, and PR creation conventions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | using-git |
| description | Use when working in the a11y-cop repository and need to perform git or GitHub operations. This is THE authoritative guidance for proper git/gh interaction in this repo, including branching, commits, and PR creation conventions. |
Authoritative guidance for git and GitHub operations in the a11y-cop repository.
Before proceeding: Read .claude/skills/using-git/IMPLEMENTATION.md for command sequences, examples, and troubleshooting.
Invoke when you need to commit changes, create branches, or create PRs in this repo. This is THE canonical source for git operations here.
| Type | Format | Example |
|---|---|---|
| Session transcripts | transcript/<YYYY-MM-DD>-cop-session | transcript/2026-05-13-cop-session |
| Artifacts | artifact/<name> | artifact/wcag-audit-template |
| Decisions | decision/<topic> | decision/axe-vs-pa11y |
| Charter changes | charter/<change-description> | charter/update-meeting-cadence |
type(scope): description
Types: docs, feat, fix, refactor, chore
Scopes: sessions, artifacts, decisions, charter
Example: docs(sessions): add cleaned transcript for 2026-05-13 CoP session
Before executing any git operations, run git status to see what changed. If sessions/ files AND other changed files (e.g. .claude/skills/, docs/, scripts/) are both present, show the proposed split and confirm before proceeding:
I found changes to commit:
Commit 1 (session notes):
sessions/2026-05-27-session-notes.md
Commit 2 (retro improvements):
.claude/skills/scribe-workflow/SKILL.md
docs/SCRIBE-WORKFLOW.md
Anything look wrong before I proceed?
If only one category of files is present, proceed with a single commit.
Then show the fully filled-in commands (real date, branch name, filenames — no placeholders) and ask:
Shall I run these, or would you like to copy-paste them yourself?
Check for gh CLI before proceeding: which gh. If not installed, skip gh pr create and provide the manual PR URL instead.
Mandatory: /scribe-retrospective — auto-analyzes friction, asks approval for changes
Optional: /workflow-feedback — captures subjective feedback, offers handling options (PR/issue/facilitator)
Sequence: Main work done → retrospective (always) → ask about feedback (optional) → git operations
See IMPLEMENTATION.md for integration details.
Branch: transcript/2026-05-13-cop-session
Commit: docs(sessions): add cleaned transcript for 2026-05-13 CoP session
PR title: Add cleaned transcript: 2026-05-13 CoP session
See IMPLEMENTATION.md for complete workflow example with commands.
gh CLI before attempting gh pr creategit add over git add .Permission template: Show fully filled-in commands → "Shall I run these, or would you like to copy-paste them yourself?"
Use when a CoP scribe has exported the Notes tab from Google Docs as markdown and needs to add frontmatter and save it to the sessions/ directory.
Use after committing a CoP session transcript. Asks if you fixed anything manually after Claude's review and updates skill tables if needed.
Use when you need to capture subjective user feedback on what didn't work well in the scribe workflow (documentation, skills, or process). Focuses only on improvements, offers options for how to handle the feedback (add to PR, create issue, or contact facilitator).
Use when a CoP scribe needs to process a Community of Practice meeting transcript after a session. Orchestrates the full workflow from cleaning the transcript through PR creation, delegating to specialized sub-skills.