code-state
Skill1 starsChanged 30 days agoMITView on GitHub
Instructions for upstream Policy A2 review of mutable module-level state and cycles in the local AST import graph, excluding TYPE_CHECKING blocks. Use before isolating tests or flattening imports and inspect the five-field evidence. Not for duplication (code-duplication) or passthrough functions (code-wrappers).
In this repository114 other files it gives its agents.
- agent-cacheSkill
- agent-compressionSkill
- agent-intelSkill
- agent-overlapSkill
- agent-stateSkill
- ambient-hudSkill
- app-testSkill
- audit-dagSkill
- auto-distillSkill
- auto-memorySkill
- auto-routerSkill
- benchSkill
- bootstrapSkill
- botte-learnSkill
- botte-nnSkill
- botte-proxySkill
- botte-wrapSkill
- cacheSkill
- call-chainsSkill
- capabilitiesSkill
- cardinalSkill
- checkupSkill
- clarificationSkill
- clusterSkill
- code-complexitySkill
- code-duplicationSkill
- code-fingerprintSkill
- code-rulesSkill
- code-wrappersSkill
- comfyuiSkill
- completion-proofSkill
- conductorSkill
- context-budgetSkill
- context-compressorSkill
- context-profilerSkill
- context-slicerSkill
- context-windowsSkill
- control-loopSkill
- cost-estimatorSkill
- dag-optimizerSkill
- dashboardSkill
- decision-ladderSkill
- demoSkill
- diff-languageSkill
- directives-auditSkill
- docgenSkill
- docs-stewardSkill
- dynamic-workflowsSkill
- efficiencySkill
- eventsSkill
- fallow-likeSkill
- fallowSkill
- fast-contextSkill
- fixSkill
- fleetSkill
- hailo-visionSkill
- harness-deltaSkill
- harvestSkill
- hermes-bridgeSkill
- hermes-second-brainSkill
- The first 60 shown.
The file
Files
code-state — anomaly A2 detector
Package scope and prerequisites
This catalog ships instructions, not the executable runtime. Python modules, scripts, local services and optional tools named below must be installed separately from the upstream project. Check their availability before running commands; if they are missing, explain the prerequisite instead of claiming execution or results. The host agent may use model tokens while following these instructions.
Commands, APIs and runtime behavior described below are conditional examples for a compatible upstream installation; they are not evidence of execution in this package.
When NOT to use
- The smell is a duplicated function body — use code_duplication.
- The smell is a chain of passthrough functions — use code_wrappers.
The upstream detector is described by A2 of the upstream docs/local-analysis-policy.md (not bundled here):
- etat_global — module-level
NAME = {}/[]/set()/dict()(and common constructors). Constants andNoneare ignored. Assignments insideif TYPE_CHECKINGare ignored. - import_circulaire — cycles in the local import graph. Relative and
absolute imports that resolve inside the scanned tree are followed.
if TYPE_CHECKINGimports are not edges.
python -m skills.code_state.cli [path]
python -m skills.code_state.cli skills --json
python -m skills.code_state.test_code_stateThe documented upstream mode is report-only; verify the installed command exit status and CI integration. Pairs with code_wrappers (A3).
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.

