scena-git-github

Synchronize and validate local git states against GitHub branches, commits, tags, issues, PRs, and releases.

18|1|Updated May 7, 2026
One-click install
npx skills add https://github.com/johannesPettersson80/scena --skill scena-git-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scena-git-github
Source: https://github.com/johannesPettersson80/scena/tree/main/.codex/skills/scena-git-github
Command: npx skills add https://github.com/johannesPettersson80/scena --skill scena-git-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align and verify local scena git state with remote GitHub state to prevent drift in branches, commits, issues, PRs, and releases.

Core Features & Use Cases

  • Compare local and remote branches, commits, and tags; validate issue and PR statuses; inspect workflow runs and release publication footprints.
  • Provide deterministic guidance for code reviews, release workflows, and CI validation across local workstations and GitHub.
  • Surface concrete evidence (git status, git log, gh commands) to justify any state differences and proposed actions.

Quick Start

Compare your local scena repository against GitHub to confirm branches, commits, and release status and surface any discrepancies.

Frequently Asked Questions about scena-git-github

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

FAQPage Schema
How do I verify local git state against GitHub remote branches and commits?

Check local and remote git state alignment by running git status and git log to compare branches, commits, and tags against GitHub. This validation surfaces concrete evidence to justify state differences and prevent drift across local workstations and remote repositories.

What is the best way to validate GitHub issue and PR statuses during a code review?

Validate GitHub issue and PR statuses during code reviews by executing gh issue view and gh pr view commands. This surfaces concrete evidence of current states and provides deterministic guidance to ensure alignment between local development and remote GitHub entities.

Can I use standard git and gh CLI commands to inspect GitHub workflow runs and release footprints?

Yes, you can inspect GitHub workflow runs and release publication footprints using standard evidence commands like gh run list. This verifies CI validation states and confirms alignment across local workstations and remote GitHub environments.

Do I need gh CLI or API access to synchronize local and remote git states?

Yes, you need access to git and GitHub via gh CLI or API to synchronize and validate local and remote states. This access is required to execute standard evidence commands that verify branches, commits, tags, issues, PRs, releases, and workflow runs.

Why does local repository state drift from GitHub remote branches and releases?

Local repository state drifts from GitHub remote branches and releases due to uncommitted changes, unpushed commits, or outdated tags. Comparing local and remote states with git log and gh commands surfaces concrete evidence to justify differences and propose corrective actions.

When do I need to align local and remote git states for release workflows?

You need to align local and remote git states for release workflows when validating release publication footprints and CI runs. Synchronizing local and GitHub states ensures branches, commits, and tags match before publishing, preventing drift in releases and workflow runs.