lina-community-commit-push-and-pr

Automate commit, push, and PR creation across LinaPro and lina-plugins submodule.

147|28|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/linaproai/linapro --skill lina-community-commit-push-and-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lina-community-commit-push-and-pr
Source: https://github.com/linaproai/linapro/tree/main/.agents/skills/lina-community-commit-push-and-pr
Command: npx skills add https://github.com/linaproai/linapro --skill lina-community-commit-push-and-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually coordinating commits, pushes, and pull requests across the LinaPro main repository and its lina-plugins submodule is time-consuming and error-prone, with high risk of creating PRs out of order, force-pushing critical changes, or leaving local branches out of sync after work is complete.

Core Features & Use Cases

  • End-to-end PR workflow automation: Handles the full process of committing submodule changes, creating and tracking the submodule PR, updating the main repo's submodule pointer only after the submodule PR is merged, and creating the main repo PR.
  • Strict safety guardrails: Enforces rules against force pushes, accidental data loss, and proceeding without confirmed PR merge status, with automatic conflict detection that stops the workflow for manual user intervention.
  • Automatic post-merge cleanup: Restores original local branches for both the submodule and main repo, and syncs them with the remote main branch after all PRs are successfully merged. Use case: LinaPro contributors updating the official plugins submodule can use this skill to avoid the common mistake of updating the main repo's submodule pointer before the submodule PR is merged, which would break the main repo's build.

Quick Start

Use the lina-community-commit-push-and-pr skill to handle the full commit, push, PR creation, and post-merge sync workflow for my changes to the lina-plugins submodule.

Frequently Asked Questions about lina-community-commit-push-and-pr

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

FAQPage Schema
How do I create a pull request for a git submodule without breaking the main repository build?

To create a pull request for a git submodule safely, the main repository's submodule pointer must only be updated after the submodule PR is fully merged. This prevents broken builds by enforcing correct PR sequencing across both repositories.

What is the correct workflow for syncing a local branch with the remote main branch after a submodule PR is merged?

Syncing a local branch after a submodule PR merge requires restoring original local branches for both the submodule and main repo, then pulling the remote main branch. This ensures both repositories remain perfectly aligned after coordinated PRs.

How do I automate git commit, push, and pull request workflows for coordinated submodule updates?

Automating git commit, push, and pull request workflows for submodule updates involves orchestrating the full end-to-end process using the GitHub CLI. This includes automatic conflict detection and strict guardrails against force pushes during the coordinated PR sequence.

Does the GitHub CLI support automatic conflict detection during automated pull request workflows?

Yes, GitHub CLI automated pull request workflows can include automatic conflict detection that halts the process for manual intervention. This enforces safety guardrails against accidental data loss and prevents proceeding without confirmed PR merge status.

Can I force push critical changes when using an automated submodule and main repo PR workflow?

No, automated submodule and main repo PR workflows enforce strict safety guardrails that explicitly prevent force pushing critical changes. These rules protect against accidental data loss and ensure safe git operations across coordinated repositories.