You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+54Lines changed: 54 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,60 @@ Use it when a Python project needs coding assistants to follow the current modul
41
41
| Platform automation | A DevEx team runs the workflow across many Python services | Python API returns structured results and readiness status |
42
42
| Contributor onboarding | New contributors need project-specific implementation rules | Generated Skills and docs describe the repo's working contracts |
The final product is a repository-owned Skill layer, not a chat transcript. Structural artifacts stay available for review, cost estimation, CI refresh, and readiness checks.
49
+
50
+
## Example Generated Skills
51
+
52
+
Generated Skills are source-cited Markdown files under `.code2skill/skills/*.md`. These shortened examples show the kind of output `code2skill` is designed to produce from repository evidence.
53
+
54
+
<details>
55
+
<summary>Repository analysis pipeline</summary>
56
+
57
+
```markdown
58
+
# Repository Analysis Pipeline
59
+
60
+
## Overview
61
+
Use this Skill when changing how code2skill scans a repository, builds evidence, or writes structural artifacts.
62
+
63
+
## Core Rules
64
+
- Keep `execute_repository(...)` as the orchestration entrypoint. Source: src/code2skill/core.py
65
+
- Resolve dependencies through `ImportGraph` before ranking files or computing affected files. Source: src/code2skill/import_graph.py, src/code2skill/impact.py
66
+
- Treat `project-summary.md`, `skill-blueprint.json`, `report.json`, and `state/analysis-state.json` as review and CI artifacts. Source: src/code2skill/core.py
67
+
68
+
## Common Flows
69
+
1. Scan candidates and extract source/config summaries.
70
+
2. Build import graph, PageRank, evidence coverage, and blueprint.
71
+
3. Render summary/reference/report artifacts before optional Skill generation.
72
+
```
73
+
74
+
</details>
75
+
76
+
<details>
77
+
<summary>Assistant target publishing</summary>
78
+
79
+
```markdown
80
+
# Assistant Target Publishing
81
+
82
+
## Overview
83
+
Use this Skill when publishing generated Skills into Codex, Claude Code, Cursor, GitHub Copilot, or Windsurf target files.
84
+
85
+
## Core Rules
86
+
- Use `adapt` for target publishing; generated target content must stay inside managed blocks or manifest-tracked files. Source: src/code2skill/adapt.py, src/code2skill/capabilities/adapt/targets.py
87
+
- Run `doctor` after adaptation to verify the bundle, Skill plan, generated Skill files, state, and selected target output. Source: src/code2skill/capabilities/adoption_service.py
`code2skill` is evaluated on structural evidence extraction before any LLM call. The benchmark compares two simple baselines against the semantic scanner used by the Skill generation pipeline.
Use this Skill when changing how code2skill scans a repository, builds evidence, or writes structural artifacts.
62
+
63
+
## Core Rules
64
+
- Keep `execute_repository(...)` as the orchestration entrypoint. Source: src/code2skill/core.py
65
+
- Resolve dependencies through `ImportGraph` before ranking files or computing affected files. Source: src/code2skill/import_graph.py, src/code2skill/impact.py
66
+
- Treat `project-summary.md`, `skill-blueprint.json`, `report.json`, and `state/analysis-state.json` as review and CI artifacts. Source: src/code2skill/core.py
67
+
68
+
## Common Flows
69
+
1. Scan candidates and extract source/config summaries.
70
+
2. Build import graph, PageRank, evidence coverage, and blueprint.
71
+
3. Render summary/reference/report artifacts before optional Skill generation.
72
+
```
73
+
74
+
</details>
75
+
76
+
<details>
77
+
<summary>Assistant target publishing</summary>
78
+
79
+
```markdown
80
+
# Assistant Target Publishing
81
+
82
+
## Overview
83
+
Use this Skill when publishing generated Skills into Codex, Claude Code, Cursor, GitHub Copilot, or Windsurf target files.
84
+
85
+
## Core Rules
86
+
- Use `adapt` for target publishing; generated target content must stay inside managed blocks or manifest-tracked files. Source: src/code2skill/adapt.py, src/code2skill/capabilities/adapt/targets.py
87
+
- Run `doctor` after adaptation to verify the bundle, Skill plan, generated Skill files, state, and selected target output. Source: src/code2skill/capabilities/adoption_service.py
f'<text x="64" y="70" font-family="Arial, sans-serif" font-size="13" fill="#4b5563">Deterministic benchmark before any LLM call; gold structural facts, n={gold_total}.</text>',
225
+
f'<text x="64" y="94" font-family="Arial, sans-serif" font-size="12" fill="#0f766e">code2skill recovers all gold facts and improves over the AST-symbol baseline by {semantic_delta:.1f} percentage points.</text>',
0 commit comments