Squad's command catalog and interactive menu. Invoke via /squad (slash command) or natural language ("squad commands", "what can squad do", "show me squad options"). Presents categorized operations (Install & Upgrade, Team Management, Issues & PRs, Plugins & Skills, Model & Cost, Sessions & State) as an interactive picker. Routes to the right squad CLI command or the Squad coordinator agent.
Internals of how @bradygaster/squad-cli stamps its version, how `squad upgrade` works (what it preserves vs overwrites), and how to probe the npm registry for the latest version from a coordinator prompt.
These instructions guide GitHub Copilot when working in this repository. This is a beginner-friendly educational course teaching GitHub Copilot CLI. The repo contains Markdown chapters (00–07), Python/C#/JavaScript sample apps, and supporting assets (images, demo GIFs, glossary). It is not a software product — it is technical courseware. These patterns were mined from actual PR review feedback and represent recurring maintainer expectations: Every chapter (00–07) follows the same pattern in its README.md: Do not deviate from this structure when editing or…
The CodeQL Action is used in GitHub Actions workflows to run CodeQL scans using the CodeQL CLI. The main codebase of the CodeQL Action is written in TypeScript and compiled to JavaScript. Both the TypeScript sources and the generated JavaScript code are contained in this repository. The TypeScript sources are contained in the src directory and the JavaScript code is contained in the lib directory. A GitHub Actions workflow checks that the JavaScript code in lib is up-to-date. Therefore, you…
A GitHub CLI (gh) extension for managing stacked branches and pull requests. Written in Go, it automates creating branches, keeping them rebased, setting PR base branches, and navigating between stack layers. Always run go vet before go test. CI runs both on every push/PR across ubuntu, windows, and macOS (test.yml). There is no Makefile, linter config, or code generation step. The standard Go toolchain is all that's needed. Each command lives in its own file (cmd/<name>.go) and follows this pattern:
A Go CLI extension (gh stack) for managing stacked branches and pull requests. Uses Cobra for commands, bubbletea/lipgloss for TUI, and stretchr/testify for tests. No Makefile, no code generation, no external linter config. Standard Go toolchain only. For full architecture details, see AGENTS.md in the repository root.
Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.
This file applies to the entire repository. It is the repository-specific instruction source for coding agents and automated contributors. Keep this file durable, small, and focused on rules that should apply every time work happens in this repository. Do not add one-off task plans, temporary investigation notes, local machine details, or long procedure transcripts here. Move detailed operating procedures to docs/, reusable workflows to skills, and directory-specific rules to a closer nested AGENTS.md if that scope ever appears. Codex loads…
This is a C# based repository that produces several CLIs that are used by customers to interact with the GitHub migration APIs. Please follow these guidelines when contributing:
Install dependencies by running: Ensure all unit tests pass by running: Unit tests should exist in the tests directory. They are powered by jest. Fixtures should be placed in the fixtures directory. - Follow standard TypeScript and JavaScript coding conventions and best practices - Changes should maintain consistency with existing patterns and style - Document changes clearly and thoroughly, including updates to existing comments when appropriate - Do not include basic, unnecessary comments that simply restate what the code is…
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.