← ClaudeAtlas

ai-agent-pr-metadatalisted

Add GitHub-visible AI agent and AI code-review metadata and exact agent labels without adding AI attribution to commits, and scope Alibaba/Open Code Review's review surface to control LLM token spend. Use when configuring PR templates, issue/PR labels, PR creation commands, PR update comments, or Alibaba Code Review/open code review workflows to disclose the implementing agent, review tool, LLM model, run URL, or to add/tune a `.opencodereview/rule.json`.
wakqasahmed/ai-engineering-workflow-skills · ★ 2 · AI & Automation · score 68
Install: claude install-skill wakqasahmed/ai-engineering-workflow-skills
# AI Agent PR Metadata Use this when a repository needs traceable AI assistance metadata in GitHub while keeping commit history human-authored and attribution-free. ## Rules - Commit attribution follows `system-level/core.md` (Git: do not add AI co-author lines or AI attribution to commit messages). This skill governs where the traceable detail goes instead: PR bodies, PR comments, and PR review bodies only. - Never guess the model name. Read the authoritative resolved model+version from the runtime or orchestrator; a product alias is not evidence of a model ID. - Include a run URL when the work was produced by GitHub Actions or another traceable runner. - Public issues, PRs, comments, and review records must never include credential values or local credential-file paths. Use `Credential details: [redacted]` instead. - Never write a third-party issue/PR reference as literal `owner/repo#123` text, or a full `https://github.com/...` URL to it, in any repo's own PR title, PR body, commit message, or issue text. This isn't only a tracker/automation-repo risk. **Both forms trigger the cross-reference**, confirmed by two separate incidents: - A tracker PR's *body* containing bare `shopware PR #20080` text created a public "mentioned this pull request" backlink on that PR's timeline, disproving an earlier (wrong) version of this rule that claimed the bare form was safe. GitHub creates this cross-reference regardless of the referencing repo's visibility: non-collaborators can't