aiasys-git-workflow

Enforce atomic commits, security checks, and branch policies for AIASys Git operations.

21|12|Updated May 17, 2026
One-click install
npx skills add https://github.com/AIAsys/AIASys --skill aiasys-git-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiasys-git-workflow
Source: https://github.com/AIAsys/AIASys/tree/main/.team-skills/aiasys-git-workflow
Command: npx skills add https://github.com/AIAsys/AIASys --skill aiasys-git-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the risk of messy, insecure, or non-compliant Git operations in the AIASys project, which can lead to unreadable code history, accidental leakage of sensitive credentials, and PRs that violate the project's branch protection rules, blocking releases.

Core Features & Use Cases

  • Standardized Commit Rules: Enforces atomic commits, explicit file staging, and structured commit messages to keep the project's Git history clear and auditable.
  • Security Guardrails: Includes pre-commit checks for sensitive files, hardcoded keys, and large unintended changes to prevent data leaks.
  • Compliant PR & Branch Workflow: Aligns with AIASys's fork-first CI, main/dev branch protection, and changelog update requirements to smooth collaboration for both contributors and maintainers.
  • Worktree & Release Management: Provides guidelines for parallel development via worktrees, release publishing checklists, and emergency handling for issues like leaked credentials.
  • Use Case: When contributing a new MCP configuration feature to AIASys, this Skill guides you to split changes into logical atomic commits, run pre-commit security and code checks, validate CI in your fork, and update the changelog before submitting a PR to the dev branch.

Quick Start

Use the aiasys-git-workflow skill to prepare a compliant pull request for your AIASys code changes, following the project's commit, security, and changelog requirements.

Frequently Asked Questions about aiasys-git-workflow

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

FAQPage Schema
How do I enforce atomic commits and prevent sensitive data leaks in git workflow?

To enforce atomic commits and prevent sensitive data leaks in git workflow, apply explicit file staging rules and pre-commit security checks for hardcoded keys. This ensures code history remains auditable and blocks accidental credential leakage.

What's the best way to prepare a pull request that complies with main and dev branch protection policies?

The best way to prepare a pull request that complies with branch protection policies is to validate CI in your fork first. Then update the changelog for user-facing changes before submitting the PR to the dev branch.

How do I manage parallel development with git worktrees for version control tasks?

To manage parallel development with git worktrees for version control tasks, follow worktree auditing guidelines. This allows multiple branches to be checked out simultaneously while maintaining strict compliance with project release publishing checklists.

Why do my pull requests get blocked by inconsistent git commits and missing changelog updates?

Your pull requests get blocked by inconsistent git commits and missing changelog updates because user-facing changes require mandatory changelog updates. Non-compliant, non-atomic commits violate branch protection rules and block releases.

What should I do to handle leaked credentials and large unintended changes before committing?

To handle leaked credentials and large unintended changes before committing, run pre-commit security checks. These guardrails detect sensitive files and large code modifications to prevent data leaks and maintain auditable version control.