Results for “git”

You have access to an environment variable, `GITLAB_TOKEN`, which allows you to interact with

GitHub CLI for issues, PRs, CI/check logs, comments, reviews, releases, repos, and gh api queries.

Expert-level guidance for GitLab CI/CD pipeline configuration, development, optimization, debugging, and best practices.

Run parallel feature work safely with Git worktrees, standardizing branch isolation, port allocation, environment sync, and cleanup for independent local development.

Create concise tldr summaries for GitHub Copilot customization files, MCP server documentation, or Copilot documentation from URLs or queries.

Bulk-migrate repo labels and Project V2 fields into GitHub org-level issue fields (single select, text, number, date).

Lock any ERC-20 token on Base for GitHub-gated vesting, linking wallet and repo to release tokens on verified pushes.

Interact with GitHub using the `gh` CLI to check PR checks, list and view CI runs, and run advanced API queries with JSON output.

Generates CI/CD pipeline configurations for Adobe App Builder projects, including GitHub Actions workflows, Azure DevOps, and GitLab CI templates with OAuth S2S secrets injection and multi-workspace promotion.

Create, list, and view GitHub issues interactively using the gh CLI.

Deletes local git branches whose upstream is gone, removing attached worktrees first.

Understand GitHub well enough to run a GTM context repo, no CS degree required. The mental model (repo, commit, branch, push, pull, clone), the operator's GUI-first workflow (GitHub Desktop, or let Claude Code handle the git), how to organize the repo, and the hard rules on what to never commit (CRM data, API keys, transcripts, pricing). The prerequisite to building a context repo. Fire on "what is a repo", "how does GitHub work", "learn git", "GitHub for GTM", "do I need to know GitHub", "clone the starter kit", "commit and push", "how do I organize my repo", or the start of building a GTM context repo.

Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member.

Generates comprehensive test strategies, task breakdowns, and quality assurance documentation for GitHub projects using ISTQB and ISO 25010 frameworks.

Reviews AWS infrastructure as code and deployed resources against the Well-Architected Framework, generating findings and GitHub issues for remediation.

Rotates GitHub account passwords and logs into security settings using an isolated browser, with manual 2FA handling and optional TOTP automation.

Interact with GitHub using the gh CLI to check CI status, list workflow runs, view logs, and query data via the API.

Create, search, triage, and label GitHub issues using the gh CLI or REST API, with guidance on avoiding duplicates and managing the backlog.

Interact with GitHub via the `gh` CLI. Use for issues (read, comment, file), pull requests (view, comment, check CI status), workflow runs, and `gh api` for queries the subcommands don't cover. Authentication is via the bot's GITHUB_TOKEN (already wired through `gh auth setup-git` at container start).

Conduct multi-round deep research on any GitHub Repo. Use when users request comprehensive analysis, timeline reconstruction, competitive analysis, or in-depth investigation of GitHub. Produces structured markdown reports with executive summaries, chronological timelines, metrics analysis, and Mermaid diagrams. Triggers on Github repository URL or open source projects.

Author and review GitHub Actions workflow YAML to ensure syntactic and structural correctness, preventing failures from unquoted expressions and other YAML-vs-Actions traps.

Generate personalized status briefings by pulling from configured data sources like GitHub, email, Teams, and Slack, then synthesizing updates in your own communication style.

Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more.

Inspect GitHub PR checks, fetch failing GitHub Actions logs, summarize failure context, then create a fix plan and implement after user approval.

Locates failing GitHub Actions checks on a pull request, fetches logs, summarizes failures, and proposes a fix plan for approval before implementing.

Runs a multi-perspective review of a pull request, including code quality, tests, and potential silent failures, then reports findings ranked by severity.

Full pull request lifecycle — create branches, commit changes, open PRs, monitor CI status, auto-fix failures, and merge. Works with gh CLI or falls back to git + GitHub REST API via curl.

Analyzes git commit history and generates structured changelogs categorized by change type.

Manage a multi-layered knowledge system for ingesting, organizing, syncing, and retrieving knowledge across local files, MCP memory, vector stores, and Git repos.

Analyze Azure resources and IaC files to identify cost optimization opportunities, calculate savings, and create GitHub issues for tracking.

Generates a concise bullet-point summary of branch changes for a pull request description, grouping related commits by theme and verifying details against actual files.

Manage GitHub repositories via the gh CLI: triage issues, review PRs, debug CI failures, create releases, and monitor security alerts.

Guides Git version control practices: branching strategies, commit conventions, merge vs rebase, conflict resolution, and pull request workflows for collaborative teams.

Integrates OWASP ZAP for Dynamic Application Security Testing in CI/CD pipelines, configuring baseline, full, and API scans, interpreting findings, tuning policies, and establishing quality gates in GitHub Actions and GitLab CI.

Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.

Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.