- Home
- Skills
- DevOps & Cloud
- StreamTeem Git Workflow
Works with the AI Agents you already use
StreamTeem Git Workflow
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
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
| Action | Status | Details |
|---|---|---|
| Final Commit | Success | feat(auth): implement oauth2 provider logic |
| Remote Merge | Success | Merged origin/main into feature/auth-provider |
| Test Suite | Passed | Unit: 120/120, Integration: 22/22 |
| Push | Success | Pushed to origin/feature/auth-provider |
| Pull Request | Created | PR #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
- Share the PR link https://github.com/org/repo-alpha/pull/42 with the backend team for review.
- Monitor the CI pipeline for any environment-specific failures.
- Switch back to
mainand rungit-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):orfix(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
- Setup mode checks repository status, fetches remote code, creates a branch, and sets the commit strategy.
- Commit mode stages finished tasks and applies conventional commit messages (for incremental strategies).
- 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
mainwithout 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.
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
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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
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
Requires
Permissions
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.