skills.rest
Kitsune-Den
Kitsune-DenOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-ritual

Coordinate commits and pull requests across multiple repositories.

Updated Apr 14, 2026
Search Tags:#git#collaboration#commits#ritual#pull-requests#cross-repo#co-author
One-click install
npx skills add https://github.com/Kitsune-Den/skulk-skills --skill git-ritual
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-ritual
Source: https://github.com/Kitsune-Den/skulk-skills/tree/main/skills/git-ritual
Command: npx skills add https://github.com/Kitsune-Den/skulk-skills --skill git-ritual

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The ceremonial process of wrapping up a work session by ensuring proper commits and PRs across multiple repositories, with lore-coded commit messages and cross-repo coordination.

Core Features & Use Cases

  • Coordinated multi-repo commit generation and PR descriptions for feature completion or session wrap-up.
  • Co-author attribution trailers in commits and structured PR narratives to document collaboration.
  • Enforced branch hygiene and consistent naming to keep history clean and auditable.

Quick Start

Tell the AI to perform the git ritual to wrap up a feature by creating commits and PRs across the relevant repositories.

Frequently Asked Questions about git-ritual

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

FAQPage Schema
How do I create coordinated commits and pull requests across multiple repositories?▼

Coordinated commits and pull requests across multiple repositories are generated by wrapping up work with standardized commit trailers, branch hygiene, and structured PR narratives to maintain clean history and auditable collaboration.

What is the best way to add co-author attribution to git commits for a multi-repo feature?▼

Co-author attribution for multi-repo features is handled by enforcing standardized commit trailers and structured PR descriptions, documenting collaboration across all relevant repositories during the wrap-up process.

How do I standardize branch hygiene and commit messages before finishing a work session?▼

Branch hygiene and commit messages are standardized during session wrap-up by enforcing consistent naming conventions and generating lore-coded commit messages to keep repository history clean and auditable.

Can I generate comprehensive PR descriptions for cross-repo coordination automatically?▼

Comprehensive PR descriptions for cross-repo coordination are generated automatically, ensuring that branch hygiene and author attribution are enforced across all repositories involved in the feature work.

When do I need to coordinate cross-repo commits and pull requests?▼

Cross-repo commits and pull requests are needed when completing multi-repo feature work or wrapping up a session, requiring coordinated messages and comprehensive PR descriptions to maintain history.

Why should I enforce standardized commit trailers and branch naming for pull requests?▼

Standardized commit trailers and branch naming should be enforced for pull requests to maintain clean git history and ensure auditable collaboration across multiple repositories during coordinated wrap-up.

Related Skills

Explore More Software Engineering Skills→
MohibShaikhMohibShaikh
11

commit

Stage changes, create a contextual commit message, and push the current branch.

Community
Intermediate
HigorAlvesHigorAlves
4

workspace-mode

Detect multi-repo workspaces and manage synchronized branching and pull request linking.

Community
Advanced
jobayerarmanjobayerarman

session-ready-for-pr

Prepare a development branch for pull request submission with validation and cleanup.

Community
Intermediate
MarcoDavaMarcoDava
1

github-multi-repo

Coordinates cross-repo changes, package versions, and architecture across multiple GitHub repositories.

Community
Advanced