Run any Skill in Manus with one click

pr-assistant

Analyzes git changes, drafts localized PR titles and bodies, and assists with creating or updating GitHub pull requests for the active agent-harness project repository. Use when working from agent-harness and the user wants to create a PR, review branch changes, draft or update a PR description, or check whether a branch is ready for review.

Run Skill in Manus

Overview

Install command

npx skills add https://github.com/atman-33/agent-harness --skill pr-assistant

Copy and paste this command into Claude Code to install the skill

Source

atman-33/agent-harness

Stars0

Forks0

UpdatedMay 31, 2026 at 07:31

File Explorer

14 files

SKILL.md

readonly

name	pr-assistant
description	Analyzes git changes, drafts localized PR titles and bodies, and assists with creating or updating GitHub pull requests for the active agent-harness project repository. Use when working from agent-harness and the user wants to create a PR, review branch changes, draft or update a PR description, or check whether a branch is ready for review.
compatibility	Requires git, GitHub CLI, and Python. PowerShell examples assume Windows.

PR Assistant

Creates reviewer-friendly PR drafts for a repository selected from the active agent-harness project.

Quick start

Read .agents/harness/config/agent-harness.yaml, resolve active_projects, and inspect the active project profiles relevant to the task.
Pick the target repository using this order: the repo named by the user; otherwise the repo owning the current file if it is unambiguous; otherwise the only repo in the active context; otherwise ask.
Run git and gh commands in the target repository root, not in the agent-harness repository root.
Save generated analysis and PR body files only under .github/skills/pr-assistant/temp-files/ in agent-harness.
Draft first and ask for approval before creating or updating the PR, unless the user explicitly asked for immediate creation.

Workflow

Resolve the target repository path from the active context.
Use Push-Location / Pop-Location or an equivalent directory stack when switching into the target repository.
Run scripts/analyze_changes.py from the target repository to produce the analysis JSON.
Choose the PR template from assets/templates/ based on branch intent, then run scripts/generate_pr_body.py.
Run scripts/quality_checks.py before presenting or creating the PR.
Present the draft and warnings to the user, or create or update the PR immediately if the user explicitly asked for that fast path.

Guardrails

Never run git or gh against the agent-harness repository unless the PR is intentionally for agent-harness itself.
Keep all temporary PR artifacts inside temp-files/ in this skill directory.
Treat a requested output language as binding for the final PR title and body.
Preserve issue references, but only emit closing keywords when the PR targets the repository default branch.
See REFERENCE.md for the full workflow, PowerShell examples, and error handling.

More from this repository

same repository

issue-to-implementation

atman-33/agent-harness

Orchestrates issue-driven development from a GitHub issue URL through feature-branch creation, spec generation, TDD-based implementation, and repository-aware validation by delegating to the existing workflow assets in the resolved repository. Use when the user provides a development issue URL and wants the branch, spec, implementation, and follow-up validation flow started or continued end-to-end.

2026-05-310

manage-agent-harness-projects

atman-33/agent-harness

Manages agent-harness project configuration, including switching the active projects, choosing the active OpenSpec source, creating project profiles, and updating work-unit repository settings. Use when working in agent-harness on .agents/harness/config/agent-harness.yaml or .agents/harness/projects/*.yaml, or when the user asks to switch projects, add a project, or change openspec_root, repos[], follow_files, or default_checks.

2026-05-310

workspace-operation-customization

atman-33/agent-harness

Create or diagnose workspace-local FF15 operation files and related facets under .ff15/operations and .ff15/facets. Use when adding or editing custom workspace operations, debugging why a workspace operation is not discoverable or routable, or validating workspace-local YAML and facet references for the VS Code extension.

2026-05-310

workspace-operation-customization

atman-33/agent-harness

2026-05-310

create-feature-branch

atman-33/agent-harness

Creates a new feature branch from main inside the intended repository after confirming the branch target and repository context. Use when the user wants to start a new feature branch, asks to create a branch for upcoming work, mentions a branch name such as feature/<name>, or another workflow has already resolved the target repository.

2026-05-240

to-issues

atman-33/agent-harness

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

2026-05-240

Source

atman-33

atman-33/agent-harness

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations15-1253L4

name	pr-assistant
description	Analyzes git changes, drafts localized PR titles and bodies, and assists with creating or updating GitHub pull requests for the active agent-harness project repository. Use when working from agent-harness and the user wants to create a PR, review branch changes, draft or update a PR description, or check whether a branch is ready for review.
compatibility	Requires git, GitHub CLI, and Python. PowerShell examples assume Windows.

PR Assistant

Creates reviewer-friendly PR drafts for a repository selected from the active agent-harness project.

Quick start

Read .agents/harness/config/agent-harness.yaml, resolve active_projects, and inspect the active project profiles relevant to the task.
Pick the target repository using this order: the repo named by the user; otherwise the repo owning the current file if it is unambiguous; otherwise the only repo in the active context; otherwise ask.
Run git and gh commands in the target repository root, not in the agent-harness repository root.
Save generated analysis and PR body files only under .github/skills/pr-assistant/temp-files/ in agent-harness.
Draft first and ask for approval before creating or updating the PR, unless the user explicitly asked for immediate creation.

Workflow

Resolve the target repository path from the active context.
Use Push-Location / Pop-Location or an equivalent directory stack when switching into the target repository.
Run scripts/analyze_changes.py from the target repository to produce the analysis JSON.
Choose the PR template from assets/templates/ based on branch intent, then run scripts/generate_pr_body.py.
Run scripts/quality_checks.py before presenting or creating the PR.
Present the draft and warnings to the user, or create or update the PR immediately if the user explicitly asked for that fast path.

Guardrails

Never run git or gh against the agent-harness repository unless the PR is intentionally for agent-harness itself.
Keep all temporary PR artifacts inside temp-files/ in this skill directory.
Treat a requested output language as binding for the final PR title and body.
Preserve issue references, but only emit closing keywords when the PR targets the repository default branch.
See REFERENCE.md for the full workflow, PowerShell examples, and error handling.