تشغيل أي مهارة في Manus بنقرة واحدة

pr-review

النجوم١

التفرعات٠

آخر تحديث٢٤ يونيو ٢٠٢٦ في ١٢:٢٢

gitculture PR workflow: branch, commit, push, PR, wait for review (Qodo + Copilot), triage, fix, reply, resolve. Includes a portability lint (no absolute /home paths, no per-user dotfile refs in committed docs) and a dry-run-default reminder for any GitHub-mutating change. Use when: creating PRs in this repo (agentculture/gitculture-cli), handling review feedback, or the user says "create PR", "review comments", "address feedback", "resolve threads".

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

agentculture

agentculture/gitculture-cli

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

محللو ضمان جودة البرمجيات والمختبرونمهن الحاسوب والرياضيات·SOC 15-1253

مستكشف الملفات

2 ملفات

SKILL.md

readonly

name

pr-review

description

PR Review — gitculture edition

gitculture's PRs touch GitHub-API surface (repo creation, environments, permissions) and AgentCulture conventions (afi-cli scaffold contract, Trusted Publishing wiring). The recurring bug classes:

Path leaks — committing absolute home-directory paths that work only on the author's machine. scripts/portability-lint.sh catches these.
Per-user config dependencies — referencing dotfiles under ~/ in repo guidance, breaking reproducibility for other contributors and CI.
Forgotten dry-run — any new GitHub-mutating verb must default to dry-run; --apply commits. This is enforced in code review (no automated check yet — flag it manually for any new repo / future pr / future issue verb).

Prerequisites

gh (GitHub CLI), bash, python3 (stdlib only). The portability lint runs against git ls-files or the staged-vs-HEAD diff; no other tooling.

Portability lint

The single committed script today. Run from the repo root:

# Lint files modified vs HEAD (default — staged + unstaged):
bash .claude/skills/pr-review/scripts/portability-lint.sh

# Lint every tracked file:
bash .claude/skills/pr-review/scripts/portability-lint.sh --all

Exits 0 if clean, 1 if a leak is found. The CI lint job runs it with --all on every PR — keep the working tree clean before pushing.

Allowed carve-outs (won't be flagged):

~/.claude/skills/<x>/scripts/ — vendored tool calls.
~/.culture/ — Culture-mesh data this skill is supposed to read (kept for parity with steward; gitculture doesn't use it today).

End-to-end flow

git checkout -b <type>/<desc>
# ... edit ...
bash .claude/skills/pr-review/scripts/portability-lint.sh
python3 .claude/skills/version-bump/scripts/bump.py {patch|minor|major}
uv run pytest -n auto -v
git commit -am "..." && git push -u origin <branch>
gh pr create --title "..." --body "..."   # title <70 chars; body signed "- Claude"
# Wait for Qodo + Copilot review (~5 min after push).
gh api repos/{owner}/{repo}/pulls/<PR>/comments
# Triage: FIX or PUSHBACK with reasoning per comment.
# Fix, re-lint, push, reply, resolve threads.
gh pr checks <PR>
# Wait for human merge — never merge yourself.

Branch naming: fix/<desc>, feat/<desc>, docs/<desc>, skill/<name>. Commit/PR signature: - Claude (workspace convention).

Triage rules

For every comment, decide FIX or PUSHBACK with reasoning.

Default to FIX for: portability complaints (always valid for this project — recurring bug class), missing dry-run on a GitHub-mutating verb, missing learn/explain entry for a new verb, test or doc requests, style nits aligned with workspace conventions.

Default to PUSHBACK for: architecture opinions that conflict with CLAUDE.md (e.g., "add a runtime dep" — gitculture is stdlib-only); requests to add features outside the alignment scope of the current PR.

Reply etiquette

Every comment must get a reply — no silent fixes. Pass --resolve when batch-replying so threads close automatically. Reference review-comment IDs in the fix-up commit message.

المزيد من هذا المستودع

نفس المستودع

bootstrap-sibling

agentculture/gitculture-cli

Bootstrap a new aligned AgentCulture sibling end-to-end: GitHub repo create, local clone, afi-cli scaffold, and pypi/testpypi Trusted-Publishing Environments. Each gitculture step dry-runs first and waits for confirmation before applying. Use when starting a new sibling (e.g. "bootstrap a new sibling called X", "create a new agentculture repo", "stand up the next sibling").

2026-06-241

doc-test-align

agentculture/gitculture-cli

Verify that claims in CLAUDE.md (GitHub endpoints, required scopes, bootstrap step order) still match what the code in `gitculture/` actually does. Run before merging anything that touches CLAUDE.md or the `gitculture.cli._commands.repo` module — catches doc drift that a normal pytest pass would not.

2026-06-241

mass-approve-prs

agentculture/gitculture-cli

Approve many pull requests at once across a whole GitHub org (or one repo), selecting them by a title heading. Composes two gitculture verbs — `gitculture pr list` (read-only org-wide search) to discover the matches and `gitculture pr approve` (one approving review each) to act — so it inherits gitculture's dry-run-default mutation safety: it shows every PR it *would* approve before you pass --apply. Per-PR failures (most often "can't approve your own pull request") are tallied, not fatal. Use when: a bot opened the same PR across many repos (a dependency bump, a skills sync, a CI change) and you want to approve all the still-open ones in one pass.

2026-06-241

mass-merge-prs

agentculture/gitculture-cli

Merge many pull requests at once across a whole GitHub org (or one repo), selecting them by a title heading. Composes two gitculture verbs — `gitculture pr list` (read-only org-wide search) to discover the matches and `gitculture pr merge` (one direct merge each) to act — so it inherits gitculture's dry-run-default mutation safety: it shows every PR it *would* merge before you pass --apply. Uses the direct merge endpoint (like `gh pr merge --admin`), so it lands PRs past NON-required failing checks such as a non-blocking `lint`; PRs blocked by a required check are tallied, not fatal. Use when: a bot opened the same PR across many repos (a rollout, a dependency bump, a skills sync) and you want to land all the still-open ones in one pass — especially when self-approval is impossible (the author is your own account) so merging is the only way to ship them.

2026-06-241

version-bump

agentculture/gitculture-cli

Bump the semver version in pyproject.toml (major, minor, or patch) and prepend a Keep-a-Changelog entry to CHANGELOG.md. Use when preparing a release, before creating a PR (the version-check CI job blocks merge if you don't), or when the user says "bump version", "release", or "increment version".

2026-06-241

recall

agentculture/gitculture-cli

Search the shared eidetic memory store and get back ranked, provenanced records. Drives `eidetic recall` with four search modes — exact (verbatim substring), approximate (vector/semantic), keyword (BM25 lexical), and hybrid (a weighted blend of vector+keyword, the default) — each hit carrying its text, full metadata, a relevance `score`, and a freshness `signal`. Recall passively reinforces matched records (bumps last_recall + recall_count). Shadowed and archived records are excluded by default; use --include-shadowed / --include-archived to retrieve them. The store lives at a repo-local ./.eidetic (rooted at the main worktree, shared across linked worktrees so the colleague backend reads the same store); the wrapper defaults queries to this agent's PERSONAL, PRIVATE scope (`--scope ghafi --visibility private`, suffix read from culture.yaml) — matching where /remember writes — so a no-flag recall returns this agent's own private records plus the shared public pool, and Claude and the colleague backend recall

2026-06-241

name

pr-review

description

PR Review — gitculture edition

gitculture's PRs touch GitHub-API surface (repo creation, environments, permissions) and AgentCulture conventions (afi-cli scaffold contract, Trusted Publishing wiring). The recurring bug classes:

Path leaks — committing absolute home-directory paths that work only on the author's machine. scripts/portability-lint.sh catches these.
Per-user config dependencies — referencing dotfiles under ~/ in repo guidance, breaking reproducibility for other contributors and CI.
Forgotten dry-run — any new GitHub-mutating verb must default to dry-run; --apply commits. This is enforced in code review (no automated check yet — flag it manually for any new repo / future pr / future issue verb).

Prerequisites

gh (GitHub CLI), bash, python3 (stdlib only). The portability lint runs against git ls-files or the staged-vs-HEAD diff; no other tooling.

Portability lint

The single committed script today. Run from the repo root:

# Lint files modified vs HEAD (default — staged + unstaged):
bash .claude/skills/pr-review/scripts/portability-lint.sh

# Lint every tracked file:
bash .claude/skills/pr-review/scripts/portability-lint.sh --all

Exits 0 if clean, 1 if a leak is found. The CI lint job runs it with --all on every PR — keep the working tree clean before pushing.

Allowed carve-outs (won't be flagged):

~/.claude/skills/<x>/scripts/ — vendored tool calls.
~/.culture/ — Culture-mesh data this skill is supposed to read (kept for parity with steward; gitculture doesn't use it today).

End-to-end flow

git checkout -b <type>/<desc>
# ... edit ...
bash .claude/skills/pr-review/scripts/portability-lint.sh
python3 .claude/skills/version-bump/scripts/bump.py {patch|minor|major}
uv run pytest -n auto -v
git commit -am "..." && git push -u origin <branch>
gh pr create --title "..." --body "..."   # title <70 chars; body signed "- Claude"
# Wait for Qodo + Copilot review (~5 min after push).
gh api repos/{owner}/{repo}/pulls/<PR>/comments
# Triage: FIX or PUSHBACK with reasoning per comment.
# Fix, re-lint, push, reply, resolve threads.
gh pr checks <PR>
# Wait for human merge — never merge yourself.

Branch naming: fix/<desc>, feat/<desc>, docs/<desc>, skill/<name>. Commit/PR signature: - Claude (workspace convention).

Triage rules

For every comment, decide FIX or PUSHBACK with reasoning.

Reply etiquette

Every comment must get a reply — no silent fixes. Pass --resolve when batch-replying so threads close automatically. Reference review-comment IDs in the fix-up commit message.