Code Guidelines
getsentry/sentry-dart
Enforce Sentry Dart/Flutter SDK code guidelines for implementation, refactoring, and review.
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
Install Extracting Code Structure
$ npx skills add SebastienDegodez/copilot-instructions --skill extracting-code-structure -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SebastienDegodez/copilot-instructions extracting-code-structure --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/extracting-code-structure .claude/skills/extracting-code-structure && 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 "extracting-code-structure" agent skill from https://github.com/SebastienDegodez/copilot-instructions/tree/main/plugins/minimal-context-tools/skills/extracting-code-structure into .claude/skills/extracting-code-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extracting-code-structure", 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/extracting-code-structureType 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 extracting-code-structure -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SebastienDegodez/copilot-instructions extracting-code-structure --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/extracting-code-structure .agents/skills/extracting-code-structure && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "extracting-code-structure" agent skill from https://github.com/SebastienDegodez/copilot-instructions/tree/main/plugins/minimal-context-tools/skills/extracting-code-structure into .agents/skills/extracting-code-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extracting-code-structure", 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 extracting-code-structure -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SebastienDegodez/copilot-instructions extracting-code-structure --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/extracting-code-structure .cursor/skills/extracting-code-structure && 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 "extracting-code-structure" agent skill from https://github.com/SebastienDegodez/copilot-instructions/tree/main/plugins/minimal-context-tools/skills/extracting-code-structure into .cursor/skills/extracting-code-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extracting-code-structure", 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/extracting-code-structure--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 extracting-code-structure -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SebastienDegodez/copilot-instructions extracting-code-structure --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/extracting-code-structure .gemini/skills/extracting-code-structure && 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 "extracting-code-structure" agent skill from https://github.com/SebastienDegodez/copilot-instructions/tree/main/plugins/minimal-context-tools/skills/extracting-code-structure into .gemini/skills/extracting-code-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extracting-code-structure", 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 extracting-code-structureInstalls 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 extracting-code-structure -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/extracting-code-structure .github/skills/extracting-code-structure && 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 "extracting-code-structure" agent skill from https://github.com/SebastienDegodez/copilot-instructions/tree/main/plugins/minimal-context-tools/skills/extracting-code-structure into .github/skills/extracting-code-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extracting-code-structure", 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 extracting-code-structure -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 extracting-code-structure --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/extracting-code-structure .opencode/skills/extracting-code-structure && 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 "extracting-code-structure" agent skill from https://github.com/SebastienDegodez/copilot-instructions/tree/main/plugins/minimal-context-tools/skills/extracting-code-structure into .opencode/skills/extracting-code-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extracting-code-structure", 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
extracting-code-structure- GitHub stars
- 197
- Token cost
- ~1.3k tokens
- SKILL.md length
- 501 words
- Files
- 2
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
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
- Works in 3 steps: Am I listing/exploring what exists? →… → Am I finding WHERE something is? →… → Am I understanding HOW something works?…
- Listing all methods
- SKILL.md covers Recognizing Structure Questions, Before You Choose a Tool, When to Get File Outline vs Read and Anti-Patterns, plus 5 more sections
- Calls yq
What it does
Extracting Code Structure is an agent skill from SebastienDegodez/copilot-instructions. Use 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
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `reference/code-structure-guide.md`).
It sits in Development. It works with Flutter and Dart. 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
- Listing all methods
- Classes in a file
- Exploring unfamiliar code
- Getting API overviews
Example prompts
- “/extracting-code-structure”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Am I listing/exploring what exists? → Structure tools
- Am I finding WHERE something is? → Search tools (Grep or ast-grep)
- Am I understanding HOW something works? → Read
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:
yq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Extracting Code Structure loads about 1.3k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 501 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). 501 words, ~1,299 tokens.
Download SKILL.mdSave it as
.claude/skills/extracting-code-structure/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- extracting-code-structure
- description
- Use 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
Code Structure Exploration Tools
Always invoke extracting-code-structure skill to extract file structure - do not execute bash commands directly.
Recognizing Structure Questions
These keywords mean use structure tools, NOT grep/search:
- "all the methods/functions/classes in..."
- "list of function signatures"
- "what functions/exports/API..."
- "package API" or "module exports"
- "method signatures with receivers" (Dart/Flutter, TypeScript)
- "what's available in..."
These keywords mean use search (Grep tool or extracting-code-structure skill):
- "where is X defined"
- "find calls to X"
- "search for pattern Y"
Before You Choose a Tool
Ask yourself:
- Am I listing/exploring what exists? → Structure tools
- Am I finding WHERE something is? → Search tools (Grep or ast-grep)
- Am I understanding HOW something works? → Read
When to Get File Outline vs Read
Get outline/index when:
- File is large (>500 lines)
- Need to see what's available (functions, classes, exports)
- Exploring unfamiliar code
- Want to decide what to read in detail
- Saves 90%+ context vs reading entire file
Just use Read when:
- File is small (<500 lines)
- Already know what you're looking for
- Need to understand implementation details
- extracting-code-structure pattern already targets what you need
Anti-Patterns
DON'T use grep/rg/Grep tool for:
- Extracting function/method lists
- Getting API overviews
- Finding all exports/public members
- Getting signatures/interfaces
These are STRUCTURE queries, not SEARCH queries.
Default Strategy
Invoke extracting-code-structure skill for extracting file structure (functions, classes, exports) efficiently without reading entire files.
Use ast-grep patterns, Dart/Flutter analyzer, ctags, or language-specific tools to get outlines and signatures. Dart/Flutter and JavaScript/TypeScript support have highest priority.
Exploration Strategy
Tiered approach (try in order):
ast-grep with known patterns - Fast, targeted (highest priority)
- Extract exports, functions, classes with specific patterns
- See code structure guide for patterns, including comprehensive Dart/Flutter support
Toolchain-specific approaches - When available
- Dart/Flutter analyzer - Comprehensive structure extraction for .dart files
- See code structure guide for Dart/Flutter patterns
- ctags/universal-ctags: Symbol index across languages
- See code structure guide for examples
- Dart/Flutter analyzer - Comprehensive structure extraction for .dart files
Read file - Last resort for exploration
- Sometimes necessary to understand structure
Show full SKILL.md (184 more words)Show less
Key Principle
Use structure tools to decide what to read, then read selectively.
Don't read 1000-line files blind. Get an outline first, then read the 50 lines you actually need.
Skill Combinations
For Discovery and Exploration
- extracting-code-structure → finding-files: Find files of a specific type, then get structure
- extracting-code-structure → searching-text: Understand structure, then search for specific patterns
- extracting-code-structure → analyzing-code-structure: Get outline, then perform structural refactoring
- extracting-code-structure → querying-json/querying-yaml: Understand API structures before extracting data
In Refactoring Workflows
- extracting-code-structure → fuzzy-selecting → analyzing-code-structure: Interactive selection of components to refactor
- extracting-code-structure → searching-text → replacing-text: Find patterns and perform replacements
For Documentation and Analysis
- extracting-code-structure → analyzing-code: Get statistics for specific code components
- extracting-code-structure → viewing-files: View structure with syntax highlighting
Multi-Skill Workflows
- extracting-code-structure → searching-text → analyzing-code-structure → viewing-files: Complete code analysis and refactoring pipeline
- extracting-code-structure → finding-files → querying-json/querying-yaml: Find and analyze configuration structures
- extracting-code-structure → fuzzy-selecting → replacing-text: Interactive selection and modification of code elements
Integration Examples
# Get structure and find all methods
ast-grep -r 'function $FUNC($$$ARGS) {$$$BODY}' src/ | fzf | cut -d: -f1 | xargs -I {} bat {}
# Understand API and extract usage
yq '.endpoints' api.yml | fzf | ripgrep -A 10 -B 5Detailed Patterns
For language-specific extraction patterns, ast-grep examples, ctags usage, and integration strategies, load code structure guide when needing:
- Dart/Flutter specific patterns and analyzer usage
- Language-specific extraction strategies
- ctags configuration and usage
- Comprehensive workflow examples
- Tool selection guidance for different languages
© 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/extracting-code-structure of SebastienDegodez/copilot-instructions.
- SKILL.md
- reference/code-structure-guide.md
Open the folder on GitHubat commit 0f0dccf
Compare with similar skills
Extracting Code Structure 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 |
|---|---|---|---|---|---|---|
| Extracting Code Structure this skillSebastienDegodez/copilot-instructions | 197 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Code Guidelinesgetsentry/sentry-dart | 873 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Bump VersionVeryGoodOpenSource/very_good_analysis | 477 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Update Dart Examples Dependenciesrodydavis/signals.dart | 819 | — | ~514 | Automated safety check: Pass | Apache-2.0 | |
| Frb Fix Merge Conflictfzyzcjy/flutter_rust_bridge | 5.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Signals Core Advanced Primitivesrodydavis/signals.dart | 819 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Bump Version
VeryGoodOpenSource/very_good_analysis
Bumps the verygoodanalysis package to a new version. An agent skill from VeryGoodOpenSource/very_good_analysis.
Update Dart Examples Dependencies
rodydavis/signals.dart
Upgrades every package under ./examples to the repository's latest signals version, runs pub upgrade on third-party dependencies, and fixes the resulting analysis problems.
Frb Fix Merge Conflict
fzyzcjy/flutter_rust_bridge
A skill your agent uses when resolving merge or rebase conflicts in flutterrustbridge, especially conflicts involving generated files after master/main changed independently from a PR branch.
Signals Core Advanced Primitives
rodydavis/signals.dart
Reference for the advanced parts of Dart's signals_core: reactive primitives, async signals, reactive collections and utility types, with a linked page for each.
Update Dependencies
sesori-ai/sesori_apps_monorepo
Weekly dependency update workflow for Sesori Apps Monorepo. An agent skill from sesori-ai/sesori_apps_monorepo.
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
Analyzing Code
SebastienDegodez/copilot-instructions
A skill your agent uses when understanding project composition by language, measuring code change impact, or generating code statistics for CI/CD metrics
Related
Categories
Questions about Extracting Code Structure
What does Extracting Code Structure do?
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. Extracting Code Structure is an agent skill from SebastienDegodez/copilot-instructions.
When should I use Extracting Code Structure?
Extracting Code Structure fits situations like: listing all methods; classes in a file; exploring unfamiliar code; getting API overviews.
How do I install Extracting Code Structure in Claude Code?
Run `npx skills add SebastienDegodez/copilot-instructions --skill extracting-code-structure -a claude-code`. Or copy the skill folder (plugins/minimal-context-tools/skills/extracting-code-structure in SebastienDegodez/copilot-instructions) into .claude/skills/extracting-code-structure in your project. Claude Code loads it when a task matches its description.
How do I install Extracting Code Structure in Codex?
Run `npx skills add SebastienDegodez/copilot-instructions --skill extracting-code-structure -a codex`. Or copy the skill folder (plugins/minimal-context-tools/skills/extracting-code-structure in SebastienDegodez/copilot-instructions) into .agents/skills/extracting-code-structure in your project. Codex loads it when a task matches its description.
Can I use Extracting Code Structure 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 extracting-code-structure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/extracting-code-structure, .gemini/skills/extracting-code-structure, .github/skills/extracting-code-structure and .opencode/skills/extracting-code-structure in your project.
What does Extracting Code Structure need to run?
Going by SKILL.md and its folder, Extracting Code Structure needs the command-line tools its instructions call (yq).
Does Extracting Code Structure access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Extracting Code Structure 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 Extracting Code Structure use?
Extracting Code Structure 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 Extracting Code Structure use?
About 1.3k tokens (SKILL.md is roughly 5.2k 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 Extracting Code Structure?
Skills that share tags, products or a category with Extracting Code Structure: Code Guidelines (getsentry/sentry-dart, 873 stars), Bump Version (VeryGoodOpenSource/very_good_analysis, 477 stars), Update Dart Examples Dependencies (rodydavis/signals.dart, 819 stars) and Frb Fix Merge Conflict (fzyzcjy/flutter_rust_bridge, 5.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Extracting Code Structure?
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.