Qcsd Cicd Swarm
proffesor-for-testing/agentic-qe
A skill your agent uses when enforcing CI/CD quality gates before release, running regression analysis, detecting flaky tests, or assessing deployment readiness in the QCSD Verification phase.
A skill your agent uses when understanding project composition by language, measuring code change impact, or generating code statistics for CI/CD metrics
Install Analyzing Code
$ npx skills add SebastienDegodez/copilot-instructions --skill analyzing-code -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SebastienDegodez/copilot-instructions analyzing-code --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/SebastienDegodez/copilot-instructions.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/minimal-context-tools/skills/analyzing-code .claude/skills/analyzing-code && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "analyzing-code" agent skill from https://github.com/SebastienDegodez/copilot-instructions/tree/main/plugins/minimal-context-tools/skills/analyzing-code into .claude/skills/analyzing-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-code", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/SebastienDegodez/copilot-instructions/tree/main/plugins/minimal-context-tools/skills/analyzing-codeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add SebastienDegodez/copilot-instructions --skill analyzing-code -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SebastienDegodez/copilot-instructions analyzing-code --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SebastienDegodez/copilot-instructions.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/minimal-context-tools/skills/analyzing-code .agents/skills/analyzing-code && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analyzing-code" agent skill from https://github.com/SebastienDegodez/copilot-instructions/tree/main/plugins/minimal-context-tools/skills/analyzing-code into .agents/skills/analyzing-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-code", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SebastienDegodez/copilot-instructions --skill analyzing-code -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SebastienDegodez/copilot-instructions analyzing-code --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SebastienDegodez/copilot-instructions.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/minimal-context-tools/skills/analyzing-code .cursor/skills/analyzing-code && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "analyzing-code" agent skill from https://github.com/SebastienDegodez/copilot-instructions/tree/main/plugins/minimal-context-tools/skills/analyzing-code into .cursor/skills/analyzing-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-code", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/SebastienDegodez/copilot-instructions.git --path plugins/minimal-context-tools/skills/analyzing-code--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add SebastienDegodez/copilot-instructions --skill analyzing-code -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SebastienDegodez/copilot-instructions analyzing-code --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SebastienDegodez/copilot-instructions.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/minimal-context-tools/skills/analyzing-code .gemini/skills/analyzing-code && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "analyzing-code" agent skill from https://github.com/SebastienDegodez/copilot-instructions/tree/main/plugins/minimal-context-tools/skills/analyzing-code into .gemini/skills/analyzing-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-code", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install SebastienDegodez/copilot-instructions analyzing-codeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add SebastienDegodez/copilot-instructions --skill analyzing-code -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SebastienDegodez/copilot-instructions.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/minimal-context-tools/skills/analyzing-code .github/skills/analyzing-code && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "analyzing-code" agent skill from https://github.com/SebastienDegodez/copilot-instructions/tree/main/plugins/minimal-context-tools/skills/analyzing-code into .github/skills/analyzing-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-code", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SebastienDegodez/copilot-instructions --skill analyzing-code -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SebastienDegodez/copilot-instructions analyzing-code --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SebastienDegodez/copilot-instructions.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/minimal-context-tools/skills/analyzing-code .opencode/skills/analyzing-code && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "analyzing-code" agent skill from https://github.com/SebastienDegodez/copilot-instructions/tree/main/plugins/minimal-context-tools/skills/analyzing-code into .opencode/skills/analyzing-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-code", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
analyzing-code- GitHub stars
- 197
- Token cost
- ~1k tokens
- SKILL.md length
- 361 words
- Files
- 2
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when understanding project composition by language, measuring code change impact, or generating code statistics for CI/CD metrics
- Understanding project composition by language
- SKILL.md covers Default Strategy, Key Options, Detailed Reference and Skill Combinations
- Calls jq, git and cargo
- Measuring code change impact
What it does
Analyzing Code is an agent skill from SebastienDegodez/copilot-instructions. Use when understanding project composition by language, measuring code change impact, or generating code statistics for CI/CD metrics
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `reference/tokei-guide.md`).
It sits in DevOps & Cloud, covering Statistics and CI/CD. The repository describes itself as: A comprehensive codebase of best practices, coding rules, and workflow automation for AI-assisted development with GitHub Copilot. Includes DDD, Clean Architecture, testing… The licence is Apache-2.0.
When your agent uses it
- Understanding project composition by language
- Measuring code change impact
- Generating code statistics for CI/CD metrics
Example prompts
- “/analyzing-code”
Requirements
- Python 3
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit 0f0dccf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
jqgitcargo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Analyzing Code loads about 1k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 361 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from SebastienDegodez/copilot-instructions at commit 0f0dccf, republished under its Apache-2.0 licence (© SebastienDegodez). 361 words, ~1,000 tokens.
Download SKILL.mdSave it as
.claude/skills/analyzing-code/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- analyzing-code
- description
- Use when understanding project composition by language, measuring code change impact, or generating code statistics for CI/CD metrics
tokei: Code Statistics Analysis
Always invoke analyzing-code skill for code statistics - do not execute bash commands directly.
Use tokei for fast, accurate code statistics across multiple languages and projects.
Default Strategy
Invoke analyzing-code skill for analyzing code statistics by language. Use when understanding project composition, measuring change impact before refactoring, or generating CI/CD metrics.
Common workflow: analyzing-code skill → other skills (finding-files, querying-json, querying-yaml) for filtering or analyzing-code skill after refactoring to measure impact.
Key Options
Basic Output Control
-f/--filesshow individual file statistics-l/--languageslist supported languages and extensions-v/--verboseshow unknown file extensions (1-3)-V/--versionshow version information--hiddeninclude hidden files-c/--columns Nset strict column width
Filtering & Exclusion
-t/--type TYPESfilter by language types (comma-separated)-e/--exclude PATTERNSexclude files/dirs (gitignore syntax)--no-ignoredon't respect ignore files--no-ignore-dotdon't respect .ignore/.tokeignore--no-ignore-vcsdon't respect VCS ignore files--no-ignore-parentdon't respect parent ignore files
Output Formats
-o/--output FORMAToutput format (json|yaml|cbor)- Requires compilation with features:
cargo install tokei --features all
- Requires compilation with features:
-i/--input FILEread from previous tokei run or stdin
Sorting Options
-s/--sort COLUMNsort by column- Possible values:
files|lines|blanks|code|comments
- Possible values:
Detailed Reference
For comprehensive usage patterns, output formats, language filtering, and integration examples, load tokei guide when needing:
- Advanced language filtering and exclusion
- JSON/YAML output processing
- CI/CD integration patterns
- Docker usage examples
- Performance tuning for large codebases
The guide includes:
- Basic usage and output control options
- Language filtering and exclusion patterns
- Output format configuration (JSON, YAML, CBOR)
- Performance tips for large codebases
- Docker usage and CI/CD integration
- Configuration files and environment variables
Show full SKILL.md (109 more words)Show less
Skill Combinations
For Discovery Phase
- finding-files → analyzing-code: Analyze specific file types or directories
- extracting-code-structure → analyzing-code: Get statistics for specific code components
- git diff → analyzing-code: Analyze changed files statistics
For Analysis Phase
- analyzing-code → querying-json/querying-yaml: Parse statistics output for reports
- analyzing-code → fuzzy-selecting: Interactive selection from language breakdown
- analyzing-code → viewing-files: View statistics with formatted output
For Refactoring Phase
- analyzing-code → replacing-text: Update configuration based on code statistics
- analyzing-code-structure → analyzing-code: Measure impact of structural changes
- analyzing-code → searching-text: Find files contributing to specific language statistics
Multi-Skill Workflows
- analyzing-code → finding-files → searching-text → analyzing-code-structure: Statistics-driven refactoring pipeline
- analyzing-code → querying-json → fuzzy-selecting: Interactive language-based file selection
- git workflow: git diff → analyzing-code → finding-files → viewing-files (analyze changes, select files, preview)
Integration Examples
# Get language breakdown and filter for top languages
tokei -o json | jq '.data | to_entries | sort_by(.value.stats.code) | reverse | .[0:5] | .[].key'
# Analyze changes after refactoring
git diff --name-only | xargs tokei --files
# Find and analyze specific components
fd -e py src/components | xargs tokei -t Python© SebastienDegodez, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in plugins/minimal-context-tools/skills/analyzing-code of SebastienDegodez/copilot-instructions.
- SKILL.md
- reference/tokei-guide.md
Open the folder on GitHubat commit 0f0dccf
Compare with similar skills
Analyzing Code next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Analyzing Code this skillSebastienDegodez/copilot-instructions | 197 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Qcsd Cicd Swarmproffesor-for-testing/agentic-qe | 494 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Monitor CInrwl/nx | 29k | 5 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Repo Hygiene Scan and FixQwenLM/qwen-code | 28k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Bash Defensive Patternspromovaweb/setupvibe | 101 | 13 repos | ~572 | Automated safety check: Pass | GPL-3.0 | |
| Winui AppLanceMcCarthy/DevOpsExamples | 172 | 1 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
Repo Hygiene Scan and Fix
QwenLM/qwen-code
Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.
Bash Defensive Patterns
promovaweb/setupvibe
Master defensive Bash programming techniques for production-grade scripts.
Winui App
LanceMcCarthy/DevOpsExamples
Bootstrap, develop, and design modern WinUI 3 desktop applications with C and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and…
Release
d-kimuson/claude-code-viewer
Run the claude-code-viewer release flow end-to-end. An agent skill from d-kimuson/claude-code-viewer.
More from SebastienDegodez/copilot-instructions
All 19 skills in this repoSetup Husky Dotnet
SebastienDegodez/copilot-instructions
A skill your agent uses when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically
Clean Architecture Dotnet
SebastienDegodez/copilot-instructions
A skill your agent uses when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD…
Outside In TDD
SebastienDegodez/copilot-instructions
A skill your agent uses when writing tests from the outside-in, defining behavior before code, or any feature where tests should start from observable business behavior and let internal design emerge
Creating Dotnet MCP Servers
SebastienDegodez/copilot-instructions
A skill your agent uses when building Model Context Protocol (MCP) servers in .NET, configuring tools, transports (SSE/stdio), JSON serialization for AOT, or testing MCP endpoints
Generate Microcks Openapi Samples
SebastienDegodez/copilot-instructions
A skill your agent uses when creating OpenAPI mock examples for Microcks, setting up request/response routing with dispatchers, or mapping request fields to mock responses
Extracting Code Structure
SebastienDegodez/copilot-instructions
A skill your agent uses when listing all methods, functions, or classes in a file, exploring unfamiliar code, getting API overviews, or deciding what to read selectively without loading entire files
Related
Questions about Analyzing Code
What does Analyzing Code do?
A skill your agent uses when understanding project composition by language, measuring code change impact, or generating code statistics for CI/CD metrics. Analyzing Code is an agent skill from SebastienDegodez/copilot-instructions.
When should I use Analyzing Code?
Analyzing Code fits situations like: understanding project composition by language; measuring code change impact; generating code statistics for CI/CD metrics.
How do I install Analyzing Code in Claude Code?
Run `npx skills add SebastienDegodez/copilot-instructions --skill analyzing-code -a claude-code`. Or copy the skill folder (plugins/minimal-context-tools/skills/analyzing-code in SebastienDegodez/copilot-instructions) into .claude/skills/analyzing-code in your project. Claude Code loads it when a task matches its description.
How do I install Analyzing Code in Codex?
Run `npx skills add SebastienDegodez/copilot-instructions --skill analyzing-code -a codex`. Or copy the skill folder (plugins/minimal-context-tools/skills/analyzing-code in SebastienDegodez/copilot-instructions) into .agents/skills/analyzing-code in your project. Codex loads it when a task matches its description.
Can I use Analyzing Code in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SebastienDegodez/copilot-instructions --skill analyzing-code -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyzing-code, .gemini/skills/analyzing-code, .github/skills/analyzing-code and .opencode/skills/analyzing-code in your project.
What does Analyzing Code need to run?
Going by SKILL.md and its folder, Analyzing Code needs the command-line tools its instructions call (jq, git and cargo). Our summary lists: Python 3; Docker.
Does Analyzing Code access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Analyzing Code safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Analyzing Code use?
Analyzing Code is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Analyzing Code use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Analyzing Code?
Skills that share tags, products or a category with Analyzing Code: Qcsd Cicd Swarm (proffesor-for-testing/agentic-qe, 494 stars), Monitor CI (nrwl/nx, 29k stars), Repo Hygiene Scan and Fix (QwenLM/qwen-code, 28k stars) and Bash Defensive Patterns (promovaweb/setupvibe, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analyzing Code?
SebastienDegodez (a GitHub user) maintains it in SebastienDegodez/copilot-instructions, which has 197 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 6, 2026.
Source: SebastienDegodez/copilot-instructions on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.