Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    StreamTeem Git Workflow

    1

    A careful Git routine in three modes: set up a feature branch without losing uncommitted work, make one conventional commit per task, then merge the latest code, run the full test suite, push, and open the pull request.

    $1.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    StreamTeem Git Workflow

    StreamTeem Git Workflow

    Example session with this skill installed

    I'm finished with the authentication feature. Merge the latest changes, run the tests, and open a PR for me.

    • Read your context and instructions
    • Compiled the streamteem git workflow

    I have completed the final steps for the authentication feature. I fetched the latest changes from origin/main, merged them into feature/auth-provider, and confirmed that the full test suite passed (142 tests successful).

    Git Workflow: Commit and PR

    Branch: feature/auth-provider
    Strategy: single
    Remote: github.com/org/repo-alpha

    ActionStatusDetails
    Final CommitSuccessfeat(auth): implement oauth2 provider logic
    Remote MergeSuccessMerged origin/main into feature/auth-provider
    Test SuitePassedUnit: 120/120, Integration: 22/22
    PushSuccessPushed to origin/feature/auth-provider
    Pull RequestCreatedPR #42 opened

    Pull Request Summary:
    Implemented the OAuth2 provider logic including token exchange and refresh flows. Linked to docs/design/auth-spec.md. Verified against the integration test suite.

    Next steps

    1. Share the PR link https://github.com/org/repo-alpha/pull/42 with the backend team for review.
    2. Monitor the CI pipeline for any environment-specific failures.
    3. Switch back to main and run git-workflow (setup) for the next work item.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Managing feature branches and PRs manually leads to messy commit histories and broken builds. This skill implements a strict, three-mode Git routine that handles everything from branch creation to pull request submission.

    What it does

    • Branch management creates feature branches from the latest remote code while preserving uncommitted local changes.
    • Conventional commits enforces standard formatting like feat(auth): or fix(ui): for all changes.
    • Commit strategies allows switching between incremental task-based commits or a single final commit.
    • Pre-push verification runs the full test and build suite automatically before any code reaches the remote.
    • PR automation merges the latest remote code, handles conflicts, pushes the branch, and generates a detailed PR description.

    How it works

    1. Setup mode checks repository status, fetches remote code, creates a branch, and sets the commit strategy.
    2. Commit mode stages finished tasks and applies conventional commit messages (for incremental strategies).
    3. Commit and PR mode performs a final merge, executes the test suite, pushes the code, and opens the pull request.

    Frameworks & tools

    The skill requires the git CLI and the gh CLI or a similar integration for opening pull requests. It is designed to work within any local development environment where unit, integration, and e2e test suites are accessible.

    Why this beats prompting it yourself

    Generic prompts often forget to fetch remote updates before pushing or skip the test suite when under pressure. This skill hard-codes safety rules that prevent pushing broken code and ensure every PR includes a summary of test results and design links.

    Use cases

    • Start a new feature branch from main without losing current experimental work.
    • Maintain a clean commit history by enforcing conventional commit rules across a team.
    • Ensure zero-regression deployments by forcing full test suite execution before push.
    • Automate the PR description process including links to design docs and test logs.

    Known limitations

    The skill cannot initialize git or force-push without explicit user permission. It requires a local environment capable of running the project's specific test commands.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    Requires git and gh CLI installed locally. Cannot resolve complex merge conflicts without user intervention. Does not support rebase workflows (uses merge).

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 4 days ago

    Software
    Git
    Optional
    gh CLI (or host CLI) for opening pull requests

    Works with local-only repos (no remote): commits locally and skips push/PR. Never force-pushes or discards uncommitted work without asking.

    Permissions

    Terminal / Shell
    Read Files
    Network Access
    Write Files

    Shell and network for git fetch/push and opening PRs. Read/write for staging files and committing. Never force-pushes or rewrites history without asking.

    Listed4 days ago

    What's inside

    Frequently Asked Questions

    The skill automates the entire Git lifecycle, from branch creation and conventional commit formatting to pre-push testing and PR creation, ensuring a clean history and preventing broken builds from reaching the remote.

    It requires a local environment with the Git CLI and GitHub CLI (gh) installed, and it is compatible with any AI agent capable of executing shell commands and accessing your local file system.

    No, the 'Setup' mode is designed to fetch the latest remote code and create a new feature branch while safely preserving your current uncommitted local changes.

    The skill is framework-agnostic and will integrate with your existing unit, integration, and E2E test commands to ensure the build passes before any code is pushed.

    You receive the skill definition files, documentation on the three operational modes (Setup, Commit, PR), and configuration instructions to link it to your project's test suite and repository.

    The skill provides a guided commit process that enforces standard prefixes (e.g., feat, fix, docs) and prompts for necessary context, ensuring your repository remains readable and professional.

    New in DevOps & Cloud