skills.rest
AIMFllys
AIMFllysCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

agent-branch-handoff

Enforces Git/PR handoff SOP for StudySolo sub-agent code and READMEs.

3|2|Updated Feb 12, 2026
Search Tags:#git#documentation#pull request#agent development#backend integration#branch workflow#code handoff
One-click install
npx skills add https://github.com/AIMFllys/StudySolo --skill agent-branch-handoff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-branch-handoff
Source: https://github.com/AIMFllys/StudySolo/tree/main/.agent/skills/agent-branch-handoff
Command: npx skills add https://github.com/AIMFllys/StudySolo --skill agent-branch-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves inconsistent, incomplete agent-branch submissions by enforcing a clear handoff SOP so reviewers and maintainers can safely integrate only the intended Agent changes into the main system.

Core Features & Use Cases

  • Branch-state aware guidance: Determines whether to create or switch to the correct feat/subagent-* branch and avoid duplicate creation.
  • Strict submission scope enforcement: Limits commits to the relevant agents/<agent-name>/ path instead of allowing git add ..
  • Mandatory README handover: Ensures the PR includes explicit main-backend integration details (including an agents.yaml snippet guidance) and clarifies whether main registration is changed.
  • Review/Merge responsibility boundaries: Clarifies that developers deliver Agent code + README, while the audit/lead handles merge analysis, main-backend completion, and docs/Updates maintenance.
  • Use Case: When building a new sub-agent or updating an existing one, it helps you generate an Agent PR plan that passes review faster and reduces integration mistakes.

Quick Start

Ask an AI to “Use the agent-branch-handoff SOP for my agent PR and tell me exactly how to prepare my branch, commit scope, and README handover fields.”

Frequently Asked Questions about agent-branch-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize agent pull request handoffs for main backend integration?▼

To standardize agent pull request handoffs, enforce a Git branch workflow on a `feat/subagent-*` branch and include a mandatory README with backend integration details. This ensures reviewers safely merge only intended agent code changes into the main system.

What should be included in a code handoff README for sub-agent development?▼

A code handoff README for sub-agent development must include explicit main-backend integration details, clarify whether main registration is changed, and provide an agents.yaml snippet. This documentation bridges the gap between developer submission and maintainer merge analysis.

How do I limit my Git commit scope when submitting agent branch code?▼

To limit your Git commit scope when submitting agent branch code, add files strictly within the relevant `agents/<agent-name>/` path. Avoid using `git add .` to ensure only intended agent-related code is included in the pull request.

When do I need to create a new Git branch for agent development submissions?▼

You need to create a new Git branch for agent development submissions when a `feat/subagent-*` branch does not already exist. This branch-state aware guidance prevents duplicate creation and ensures you switch to the correct branch before committing.

Who is responsible for docs/Updates maintenance after an agent PR merge?▼

Responsibility for docs/Updates maintenance after an agent PR merge falls on the audit lead. Developers deliver the agent code and README handover, while the audit lead handles merge analysis, main-backend completion, and post-merge documentation.

Does this agent branch workflow allow submitting non-agent code in the same pull request?▼

No, this agent branch workflow enforces strict submission scope, meaning non-agent code is not allowed. It limits commits exclusively to the relevant `agents/<agent-name>/` path to prevent inconsistent and incomplete main repository integrations.

Related Skills

Explore More Software Engineering Skills→
berkcangumusisikberkcangumusisik
11

pr-create

Generate GitHub pull requests from the current branch with gh.

Community
Intermediate
arbazkhan971arbazkhan971
26

finish

Finalize feature branches via merge, pull request, keep, or discard after build, lint, and tests.

Community
Advanced
timequitytimequity
6

verification-gate

Automates verification of tests, builds, linting, and security checks before completion.

Official
Intermediate
intrusive-memoryintrusive-memory

release

Merge pull requests, create annotated Git tags, and generate GitHub releases.

Official
Advanced