devtu-github

Automate GitHub pushes with pre-commit hooks, pytest, and rebase workflows.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Centaurioun/osteogenesis_imperfecta --skill devtu-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devtu-github
Source: https://github.com/Centaurioun/osteogenesis_imperfecta/tree/main/.agents/skills/devtu-github
Command: npx skills add https://github.com/Centaurioun/osteogenesis_imperfecta --skill devtu-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a safe, repeatable workflow to fix GitHub CI failures and prevent accidental commits of temporary or sensitive files, reducing broken builds and failing pull requests.

Core Features & Use Cases

  • Pre-push cleanup: Move root-level session markdown and ad-hoc test scripts out of the repository to avoid accidental commits.
  • Pre-commit and lint/test orchestration: Install and activate pre-commit hooks, run ruff formatting and checks, and execute pytest locally to reproduce CI failures.
  • Git hygiene and push workflow: Stage specific files, rebase onto the latest main, resolve conflicts, and push safely using force-with-lease when appropriate.
  • Use Case: A developer receives failing CI on a PR, reproduces the failure locally, applies the pattern-based fixes (e.g., return_message=True, mock fixes, lint fixes), and pushes a clean rebased commit.

Quick Start

Install and activate pre-commit, run the test suite locally to identify failures, move any root temp files into temp_docs_and_tests/, stage only the files you intend to change, rebase onto origin/main, and push with --force-with-lease.

Frequently Asked Questions about devtu-github

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

FAQPage Schema
How do I fix failing pytest tests before pushing to GitHub CI?

To fix failing pytest tests before pushing, run pytest locally to reproduce CI failures, apply pattern-based fixes like return_message=True or mock adjustments, stage specific files, rebase onto origin/main, and push safely using force-with-lease.

How do I prevent temporary files from being committed in GitHub pre-commit hooks?

To prevent temporary files from being committed, move root-level session markdown and ad-hoc test scripts into a temp_docs_and_tests directory, then run pre-commit install and hooks to ensure clean staging before pushing.

What is the safest way to rebase commits and push to GitHub without overwriting remote changes?

The safest way to rebase and push without overwriting remote changes is to rebase onto the latest origin/main, resolve any conflicts locally, and use git push with the --force-with-lease flag to ensure remote integrity.

Can I run ruff formatting and pre-commit hooks locally to reproduce GitHub CI failures?

Yes, you can run ruff formatting and pre-commit hooks locally to reproduce GitHub CI failures by installing pre-commit, activating the hooks, and executing the checks on your staged files before pushing to the remote repository.

Why does my GitHub CI pipeline fail on untracked files after a local pytest run?

Your GitHub CI pipeline fails because untracked temporary session files and ad-hoc test scripts remain in the repository root; moving them out and staging only intended changes prevents broken builds and failing pull requests.