Devtu Github

What it does

The Devtu Github skill automates a specific workflow for pushing ToolUniverse code to GitHub, ensuring quality and preventing common errors. It enforces a multi-phase process including cleaning up temporary files, activating pre-commit hooks for automated checks (linting, formatting, YAML/TOML validation, whitespace removal), running the full test suite locally, and carefully staging only necessary files before committing and pushing. This workflow aims to maintain code quality and minimize merge conflicts.

When to use it

• When preparing ToolUniverse code for a push to GitHub.
• To ensure pre-commit hooks are active and functioning correctly.
• Before creating a commit, to validate code style and run tests locally.
• To avoid pushing temporary files or credential information to the repository.
• To rebase changes onto the latest origin/main branch before pushing.

Key capabilities

• Pre-Push Cleanup: Moves temporary markdown files (session documentation) and ad-hoc test scripts out of the root directory.
• Pre-Commit Hook Activation: Installs and activates pre-commit hooks for automated code checks.
• Automated Checks: Runs ruff check --fix (linting with auto-fix), ruff format, YAML/TOML validation, trailing whitespace removal, and end of file fixes during commit.
• Test Execution: Executes the full test suite locally using pytest.
• Selective Staging: Encourages staging only specific files instead of adding all changes.
• Rebasing: Promotes rebasing onto the latest origin/main branch before pushing to prevent merge conflicts.

Example prompts

• "Run the pre-push cleanup for my ToolUniverse code."
• "Activate and verify the pre-commit hooks."
• "Execute the full test suite locally."
• "Prepare a commit, ensuring all checks pass."

Tips & gotchas

• This skill is specifically designed for ToolUniverse code.
• Avoid using git add . or git add -A; always stage files selectively.
• Always rebase onto the latest origin/main branch before pushing to minimize merge conflicts.