Secure CLI to manage multiple GitHub/GitLab accounts with per-folder git credentials
Custom status line for Claude Code CLI with model, git, context, cost, and usage timer
Git context plugin for Kuzo MCP — detects repo, branch, and working tree state.
Persistent session HUD widget for Pi (below-editor bar with git/context/model/activity).
Shared core library for ai-plugins-cc: state, process, git, context, render, job-control, tracked-jobs, workspace, fs, args, prompts.
Codebase-aware prompt enhancer for the Pi coding agent — rewrites rough prompts into precise ones, with project tree, git context, and referenced file contents, before they reach the model.
Audit trail for Claude Code: persist every user prompt with session, directory, and git context to a JSON file.
CLI tool that gathers and structures repository context for AI-powered code reviews
Datadog CI plugin for `sbom` commands
Easy to check and switch git commit author. For multi git context user.
Datadog CI plugin for `sarif` commands
OpenCode plugin that displays timestamp, session duration, and git context on each prompt
This is an internal utility, not intended for public usage.
Framework-agnostic primitives shared by @withpanache/nextjs and @withpanache/cli: lockfile detection, deps manifest parsing, git context detection, CSP parsing/injection, and ingest API helpers.
View docs [here](https://radix-ui.com/primitives/docs/components/context-menu).
Opinionated git state context injection for pi
OpenTelemetry AsyncLocalStorage-based Context Manager
Provides metadata and conversions from repository urls for GitHub, Bitbucket and GitLab
A flexible way to handle safe area, also works on Android and web.
Universal Virtual Machine for Node and Browser
Provide context info for eslint-plugin-import-x, so no extra arguments need to be added.
Tiny helpers for processing regex syntax
MCP server for SpecSync - Git context and cross-repo Bridge sync tools
Invoke scoped data storage for AWS Lambda Node.js Runtime Environment
A Git extension for managing multiple repositories within a single working directory.
A Capsula context that captures Git repository information.
`git-context` provides a tool to manage conditional git config.
A collection of Rake tasks designed to represent Git Flow in a Ruby context.
User management and pairing for Git
ace-git gives developers and coding agents focused git context commands and guided workflows for rebases, pull requests, and commit reorganization, with smart diff output and Git 2.23+ guardrails.
git-spelunk is a terminal based exploration tool for git blame and history, based on the notion of moving in history based on file context
Memoflow captures git-backed development context and exposes a lightweight query API for AI assistants.
Commit AI automates the generation of insightful single-line and multi-line commit messages by analyzing staged git diffs with OpenAI's advanced language models. It allows users to provide optional change descriptions for better context, and smartly minifies the git diff to focus on the essential changes, ensuring clarity and best practices.
DevContext (aka `dx`) is a developer context manager that unifies directory-level context switching, branch awareness, multi-repo awareness, and Git-aware introspection. It helps you manage multiple active projects with an active stack.
CodeHealer is a revolutionary gem that enables your Ruby applications to automatically detect, analyze, and fix errors using AI. It integrates with OpenAI API, Claude Code terminal, and provides intelligent error handling, business context awareness, and automated Git operations. Features: - 🤖 AI-powered error analysis and code generation - 🎯 Business context-aware fixes - 🔄 Multiple healing strategies (API, Claude Code, Hybrid) - 📝 Automated Git operations and PR creation - 📋 Business requirements integration from markdown - ⚡ Background job processing with Sidekiq - 🎨 Configurable via YAML files
TrakFlow is a specialized task tracking system designed for robots. It implements a dependency-aware graph, allowing robots to handle complex/lengthy task workflows without losing context. Tasks are stored as JSONL files within a designated directory, using Git as the underlying database for versioning, branching, and merging.
{<img src="https://secure.travis-ci.org/socialcast/socialcast-shoulda-ext.png?branch=master" alt="Build Status" />}[http://travis-ci.org/socialcast/socialcast-shoulda-ext] = Socialcast Shoulda Extensions Adds new matchers and functionality to the shoulda test library = Installation In your Gemfile: group :test do gem 'socialcast_shoulda_ext', :git => 'git@github.com:socialcast/socialcast-shoulda-ext.git', :require => 'shoulda_ext' end If you want to include the trigger_callbacks matcher, also add the following to your test helper: ShouldaExt::Matchers::TriggerCallbackMatcher.attach_active_record_callback_hooks! = Matchers == RecordCountChangeMatcher Test if the count for a model has changed, and by how much. Requires the context_with_matcher_before_hooks patch, which is included by default. Provides the following matcher methods: - create_record(klass_or_symbol) Alias for change_record_count.for(klass_or_symbol).by(1) - create_records(klass_or_symbol, amount) Alias for change_record_count.for(klass_or_symbol).by(amount) - destroy_record(klass_or_symbol) Alias for change_record_count.for(klass_or_symbol).by(-1) - destroy_records(klass_or_symbol, amount) Alias for change_record_count.for(klass_or_symbol).by(-amount) - change_record_count Tests the difference in record count before and after the current setup/subject block Can be used with the follow methods: - for(klass_or_symbol) Provides the class which the test is being performed on. Can be a constant or a symbol - by(amount) Provides an expected difference for the number of records for the specified class. Excluding this number will allow the matcher to check for any difference Examples: context "creating a blog article" do context "with good parameters" do setup do post :create, :blog => {:title => 'my blog post', :body => 'Ipsum lorem...'} end should create_record :blog end context "without a body" do setup do post :create, :blog => {:title => 'my blog post' } end should_not create_record Blog end end == RespondWithJson Check if the controller's response is json Examples: context ":index.json" do setup do get :index, :format => 'json' end # Just check to see that the response was json should respond_with_json # Evaluate the hash produced by the json yourself should respond_with_json { |json| json.first['blog']['title'] == 'blog post 1'} # Provide an exact match should respond_with_json.exactly(['blog' => {'id' => 1, 'title' => 'blog post 1'}]) # Provide an exact match with a block should response_with_json.exactly{ |json| JSON.parse(Blog.all.to_json)} end context ":index.html" do setup do get :index end # or the negation should_not respond_with_json end == TriggerCallbackMatcher Test if create, update, destroy, or save callbacks were triggered. Requires running ShouldaExt::Matchers::TriggerCallbackMatcher.attach_active_record_callback_hooks! in your test suite in order to work properly. Examples: context "doing nothing to a record" do subject { Blog.new :title => 'blog title' } should_not trigger_callbacks end context "creating a record" do subject { Blog.create! :title => 'blog title' } should trigger_callbacks.for :create should_not trigger_callbacks.for :update, :destroy end = Integrations Currently only integrates with test/unit. RSpec support to come. = Shoulda Extensions == ContextWithMatcherBeforeHooks Adds the ability to define a 'before' method on any method which will be run before each context's setup/subject block. Used by RecordCountChangeMatcher to record the number of records before the tested operation takes place.
Diff and patch tables
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.