gitnexus-area-enrichment
Skill1 starsChanged 51 days agoMITView on GitHub
Skill for the Enrichment area of slopgate. 154 symbols across 18 files.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Start here when exploring this area:
- Distinctive: line 85
Read key files listed above for implementation details
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
Enrichment
154 symbols | 18 files | Cohesion: 65%
When to Use
- Working with code in
src/ - Understanding how pretool_write_payload, make_sibling_test, write_text work
- Modifying enrichment-related functionality
Key Files
| File | Symbols |
src/slopgate/enrichment/code_enrichers.py | _base_name, _build_long_params_extras, _decorator_is_dataclass, _grouped_type_hints, _parameter_names (+14) |
tests/enrichment/test_01_discover_fixtures_to_pytest003_enrichment.py | test_loop_assert_regex_does_not_backtrack_on_large_patch, test_still_denies_without_fixtures, test_handles_syntax_error_in_conftest, test_no_conftest_returns_empty, test_caps_at_max (+12) |
src/slopgate/enrichment/pytest_enrichers.py | _first_hit_path, _hit_path_and_fixtures, _resolve_hit_path, enrich_fixture_outside_conftest, _append_fixture_enrichment (+10) |
tests/enrichment/test_03_pycode008_enrichment_to_pyexc002_enrichment.py | _thin_wrapper_reason_with_call_site, test_thin_wrapper_cites_repo_local_call_sites, test_thin_wrapper_lists_boundary_checklist, test_includes_common_exceptions, test_lists_called_functions (+8) |
tests/enrichment/test_04_pylog001_enrichment_to_enrichment_constant_index_scope.py | test_unrelated_quality_rule_does_not_build_constant_index, test_finds_path_config, test_suggests_pathlib_pattern, test_finds_constants_module, test_names_triggered_literals_and_lines (+7) |
tests/enrichment/test_03_pytest_enrichers_direct.py | _context, _enriched_finding, _prepare_fixture_project, _prepare_loop_project, _prepare_test_file (+7) |
src/slopgate/enrichment/_helpers.py | append_enrichment_message, first_target_content, get_parse_count, reset_parse_count, safe_read (+5) |
tests/enrichment/test_02_pytest001_enrichment_to_regression_fixtures.py | test_enrichment_error_swallowed, test_includes_split_tip, test_suggests_creating_conftest, test_suggests_callable_for_callbacks, test_suggests_typeddict_for_dicts (+4) |
src/slopgate/enrichment/type_enrichers.py | _collect_suppressions, _describe_suppression, _suppression_advice, _suppression_description, enrich_type_suppression (+4) |
src/slopgate/enrichment/logger_enrichers.py | _dependency_hints, _dependency_in_pyproject, _dependency_in_requirements, enrich_boundary_logger, _append_dependency_hints (+4) |
Entry Points
Start here when exploring this area:
pretool_write_payload(Function) —tests/test_enrichment.py:62make_sibling_test(Function) —tests/test_enrichment.py:49write_text(Function) —tests/test_enrichment.py:27make_conftest(Function) —tests/test_enrichment.py:31mkdir(Function) —tests/test_enrichment.py:23
Key Symbols
| Symbol | Type | File | Line |
pretool_write_payload | Function | tests/test_enrichment.py | 62 |
make_sibling_test | Function | tests/test_enrichment.py | 49 |
write_text | Function | tests/test_enrichment.py | 27 |
make_conftest | Function | tests/test_enrichment.py | 31 |
mkdir | Function | tests/test_enrichment.py | 23 |
finding | Function | tests/enrichment/test_03_pytest_enrichers_direct.py | 30 |
test_enrich_assertion_roulette_adds_fixture_names_and_split_tip | Function | tests/enrichment/test_03_pytest_enrichers_direct.py | 102 |
test_enrich_fixture_outside_conftest_suggests_nearest_registry | Function | tests/enrichment/test_03_pytest_enrichers_direct.py | 138 |
test_enrich_test_loop_adds_fixture_parametrize_and_context | Function | tests/enrichment/test_03_pytest_enrichers_direct.py | 82 |
test_enrich_test_smells_mentions_fixtures_and_time_utilities | Function | tests/enrichment/test_03_pytest_enrichers_direct.py | 118 |
discover_fixtures | Function | src/slopgate/enrichment/fixtures.py | 72 |
enrich_fixture_outside_conftest | Function | src/slopgate/enrichment/pytest_enrichers.py | 197 |
append_enrichment_message | Function | src/slopgate/enrichment/_helpers.py | 22 |
first_target_content | Function | src/slopgate/enrichment/_helpers.py | 30 |
enrich_silent_except | Function | src/slopgate/enrichment/silent_except.py | 38 |
enrich_type_suppression | Function | src/slopgate/enrichment/type_enrichers.py | 152 |
enrich_findings | Function | src/slopgate/enrichment/__init__.py | 139 |
get_parse_count | Function | src/slopgate/enrichment/_helpers.py | 63 |
reset_parse_count | Function | src/slopgate/enrichment/_helpers.py | 57 |
safe_read | Function | src/slopgate/enrichment/_helpers.py | 37 |
Execution Flows
| Flow | Type | Steps |
Enrich_findings → _locked_file | cross_community | 7 |
Enrich_findings → _path_lock_for | cross_community | 7 |
Enrich_test_loop → _decorator_target | cross_community | 5 |
Enrich_test_loop → _is_fixture_target | cross_community | 5 |
Enrich_thin_wrapper → Resolve_path | cross_community | 4 |
Enrich_thin_wrapper → Safe_read | cross_community | 4 |
Enrich_long_method → _block_description | intra_community | 4 |
Enrich_test_loop → Safe_parse | cross_community | 4 |
Enrich_test_loop → _iter_conftest_paths | cross_community | 4 |
Enrich_test_loop → _first_hit_path | cross_community | 4 |
How to Explore
context({name: "pretool_write_payload"})— see callers and calleesquery({search_query: "enrichment"})— find related execution flows- Read key files listed above for implementation details
explain({target: "<file or symbol>"})— persisted taint findings (source→sink data flows), when indexed with--pdg
In this repository115 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/backend.mdcCursor rule
- .cursor/rules/commit.mdcCursor rule
- .cursor/rules/database.mdcCursor rule
- .cursor/rules/debug.mdcCursor rule
- .cursor/rules/design.mdcCursor rule
- .cursor/rules/dev-workflow.mdcCursor rule
- .cursor/rules/frontend.mdcCursor rule
- .cursor/rules/i18n-arb.mdcCursor rule
- .cursor/rules/i18n-guide.mdcCursor rule
- .cursor/rules/infrastructure.mdcCursor rule
- .cursor/rules/market.mdcCursor rule
- .cursor/rules/mobile.mdcCursor rule
- .cursor/rules/quality.mdcCursor rule
- beadsSkill
- gitnexus-area-adaptersSkill
- gitnexus-area-cliSkill
- gitnexus-area-contextSkill
- gitnexus-area-dashboardSkill
- gitnexus-area-detectorsSkill
- gitnexus-area-engineSkill
- gitnexus-area-hooksSkill
- gitnexus-area-installerSkill
- gitnexus-area-integrationSkill
- gitnexus-area-lintSkill
- gitnexus-area-payloadsSkill
- gitnexus-area-project-indexSkill
- gitnexus-area-resourcesSkill
- gitnexus-area-rules-2Skill
- gitnexus-area-rulesSkill
- gitnexus-area-scriptsSkill
- gitnexus-area-test-smellsSkill
- gitnexus-area-testsSkill
- gitnexus-area-uiSkill
- gitnexus-cliSkill
- gitnexus-debuggingSkill
- gitnexus-exploringSkill
- gitnexus-guideSkill
- gitnexus-impact-analysisSkill
- gitnexus-refactoringSkill
- impeccableSkill
- oma-academic-writingSkill
- oma-architectureSkill
- oma-backendSkill
- oma-brainstormSkill
- oma-coordinationSkill
- oma-dbSkill
- oma-debugSkill
- oma-deepsecSkill
- oma-designSkill
- oma-dev-workflowSkill
- oma-docsSkill
- oma-explanationSkill
- oma-frontendSkill
- oma-hwpSkill
- oma-imageSkill
- oma-marketSkill
- oma-mobileSkill
- oma-observabilitySkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.