elelem-skills 0.2.0 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (41) hide show
  1. checksums.yaml +4 -4
  2. data/.agents/backlog/001-enforce-pinned-digests.md +71 -0
  3. data/.agents/backlog/002-refresh-skill-tool-description.md +64 -0
  4. data/.agents/backlog/003-redirect-status-handling.md +47 -0
  5. data/.agents/backlog/004-private-address-fetches.md +58 -0
  6. data/.agents/backlog/005-release-changelog-fixes.md +47 -0
  7. data/.agents/backlog/006-gem-metadata-links.md +65 -0
  8. data/.github/workflows/release.yml +63 -0
  9. data/.release-please-manifest.json +3 -0
  10. data/.rspec +1 -0
  11. data/.rubocop.yml +62 -0
  12. data/CHANGELOG.md +22 -0
  13. data/README.md +3 -0
  14. data/Rakefile +5 -1
  15. data/exe/elelem-skills +6 -0
  16. data/lib/elelem/skills/catalog.rb +74 -0
  17. data/lib/elelem/skills/cli.rb +55 -0
  18. data/lib/elelem/skills/fetcher.rb +164 -0
  19. data/lib/elelem/skills/lockfile.rb +56 -0
  20. data/lib/elelem/skills/setup.rb +88 -0
  21. data/lib/elelem/skills/skill.rb +6 -4
  22. data/lib/elelem/skills/skill_file.rb +42 -0
  23. data/lib/elelem/skills/version.rb +1 -1
  24. data/lib/elelem/skills.rb +13 -0
  25. data/release-please-config.json +12 -0
  26. data/spec/elelem/skills/catalog_spec.rb +122 -0
  27. data/spec/elelem/skills/cli_spec.rb +66 -0
  28. data/spec/elelem/skills/fetcher_spec.rb +282 -0
  29. data/spec/elelem/skills/lockfile_spec.rb +51 -0
  30. data/spec/elelem/skills/setup_spec.rb +124 -0
  31. data/spec/elelem/skills/skill_file_spec.rb +79 -0
  32. data/spec/elelem/skills/skill_spec.rb +11 -0
  33. data/spec/fixtures/skills/no-description/SKILL.md +5 -0
  34. data/spec/fixtures/skills/tdd/SKILL.md +8 -0
  35. data/spec/spec_helper.rb +13 -0
  36. metadata +92 -16
  37. data/lib/elelem/skills/prompts/build.erb +0 -39
  38. data/lib/elelem/skills/prompts/design.erb +0 -41
  39. data/lib/elelem/skills/prompts/plan.erb +0 -59
  40. data/lib/elelem/skills/prompts/review.erb +0 -44
  41. data/lib/elelem/skills/prompts/verify.erb +0 -39
metadata CHANGED
@@ -1,52 +1,128 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: elelem-skills
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.2.0
4
+ version: 0.4.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - mo khan
8
- bindir: bin
8
+ bindir: exe
9
9
  cert_chain: []
10
10
  date: 1980-01-02 00:00:00.000000000 Z
11
11
  dependencies:
12
12
  - !ruby/object:Gem::Dependency
13
13
  name: elelem
14
+ requirement: !ruby/object:Gem::Requirement
15
+ requirements:
16
+ - - ">="
17
+ - !ruby/object:Gem::Version
18
+ version: 0.13.1
19
+ - - "<"
20
+ - !ruby/object:Gem::Version
21
+ version: '1'
22
+ type: :runtime
23
+ prerelease: false
24
+ version_requirements: !ruby/object:Gem::Requirement
25
+ requirements:
26
+ - - ">="
27
+ - !ruby/object:Gem::Version
28
+ version: 0.13.1
29
+ - - "<"
30
+ - !ruby/object:Gem::Version
31
+ version: '1'
32
+ - !ruby/object:Gem::Dependency
33
+ name: json
34
+ requirement: !ruby/object:Gem::Requirement
35
+ requirements:
36
+ - - "~>"
37
+ - !ruby/object:Gem::Version
38
+ version: '3.0'
39
+ type: :runtime
40
+ prerelease: false
41
+ version_requirements: !ruby/object:Gem::Requirement
42
+ requirements:
43
+ - - "~>"
44
+ - !ruby/object:Gem::Version
45
+ version: '3.0'
46
+ - !ruby/object:Gem::Dependency
47
+ name: net-http
48
+ requirement: !ruby/object:Gem::Requirement
49
+ requirements:
50
+ - - "~>"
51
+ - !ruby/object:Gem::Version
52
+ version: '0.9'
53
+ type: :runtime
54
+ prerelease: false
55
+ version_requirements: !ruby/object:Gem::Requirement
56
+ requirements:
57
+ - - "~>"
58
+ - !ruby/object:Gem::Version
59
+ version: '0.9'
60
+ - !ruby/object:Gem::Dependency
61
+ name: yaml
14
62
  requirement: !ruby/object:Gem::Requirement
15
63
  requirements:
16
64
  - - "~>"
17
65
  - !ruby/object:Gem::Version
18
- version: '0.11'
66
+ version: '0.4'
19
67
  type: :runtime
20
68
  prerelease: false
21
69
  version_requirements: !ruby/object:Gem::Requirement
22
70
  requirements:
23
71
  - - "~>"
24
72
  - !ruby/object:Gem::Version
25
- version: '0.11'
26
- description: Skills loader for for elelem.
73
+ version: '0.4'
74
+ description: Discovers and loads .agents/skills/*/SKILL.md skills (per the agent skills
75
+ standard) as an elelem tool and /skills command.
27
76
  email:
28
77
  - mo@mokhan.ca
29
- executables: []
78
+ executables:
79
+ - elelem-skills
30
80
  extensions: []
31
81
  extra_rdoc_files: []
32
82
  files:
83
+ - ".agents/backlog/001-enforce-pinned-digests.md"
84
+ - ".agents/backlog/002-refresh-skill-tool-description.md"
85
+ - ".agents/backlog/003-redirect-status-handling.md"
86
+ - ".agents/backlog/004-private-address-fetches.md"
87
+ - ".agents/backlog/005-release-changelog-fixes.md"
88
+ - ".agents/backlog/006-gem-metadata-links.md"
89
+ - ".github/workflows/release.yml"
90
+ - ".release-please-manifest.json"
91
+ - ".rspec"
92
+ - ".rubocop.yml"
93
+ - CHANGELOG.md
33
94
  - LICENSE.txt
95
+ - README.md
34
96
  - Rakefile
97
+ - exe/elelem-skills
35
98
  - lib/elelem/skills.rb
36
- - lib/elelem/skills/prompts/build.erb
37
- - lib/elelem/skills/prompts/design.erb
38
- - lib/elelem/skills/prompts/plan.erb
39
- - lib/elelem/skills/prompts/review.erb
40
- - lib/elelem/skills/prompts/verify.erb
99
+ - lib/elelem/skills/catalog.rb
100
+ - lib/elelem/skills/cli.rb
101
+ - lib/elelem/skills/fetcher.rb
102
+ - lib/elelem/skills/lockfile.rb
103
+ - lib/elelem/skills/setup.rb
41
104
  - lib/elelem/skills/skill.rb
105
+ - lib/elelem/skills/skill_file.rb
42
106
  - lib/elelem/skills/version.rb
43
- homepage: https://src.mokhan.ca/elelem/skills
107
+ - release-please-config.json
108
+ - spec/elelem/skills/catalog_spec.rb
109
+ - spec/elelem/skills/cli_spec.rb
110
+ - spec/elelem/skills/fetcher_spec.rb
111
+ - spec/elelem/skills/lockfile_spec.rb
112
+ - spec/elelem/skills/setup_spec.rb
113
+ - spec/elelem/skills/skill_file_spec.rb
114
+ - spec/elelem/skills/skill_spec.rb
115
+ - spec/fixtures/skills/no-description/SKILL.md
116
+ - spec/fixtures/skills/tdd/SKILL.md
117
+ - spec/spec_helper.rb
118
+ homepage: https://elelem.sh
44
119
  licenses:
45
120
  - MIT
46
121
  metadata:
47
122
  allowed_push_host: https://rubygems.org
48
- homepage_uri: https://src.mokhan.ca/elelem/skills
49
- source_code_uri: https://src.mokhan.ca/elelem/skills
123
+ homepage_uri: https://elelem.sh
124
+ source_code_uri: https://github.com/elelem-sh/skills
125
+ rubygems_mfa_required: 'true'
50
126
  rdoc_options: []
51
127
  require_paths:
52
128
  - lib
@@ -61,7 +137,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
61
137
  - !ruby/object:Gem::Version
62
138
  version: '0'
63
139
  requirements: []
64
- rubygems_version: 4.0.20
140
+ rubygems_version: 4.0.6
65
141
  specification_version: 4
66
- summary: Skills loader for for elelem.
142
+ summary: Skill loader for elelem.
67
143
  test_files: []
@@ -1,39 +0,0 @@
1
- Terminal coding agent. Execute tasks from a story.
2
-
3
- # Role
4
- - Work through Tasks in the story the user specifies
5
- - Check off completed tasks
6
- - Follow TDD: write failing test, implement, refactor
7
-
8
- # Process
9
- 1. **Focus** - Ask which story to work on if not specified
10
- 2. **Read** - Load the story from .elelem/backlog/
11
- 3. **Test** - Write failing test first
12
- 4. **Implement** - Minimal code to pass
13
- 5. **Verify** - Run tests
14
- 6. **Check** - Mark task complete in story file
15
-
16
- # Editing
17
- Multi-line: `echo "DIFF" | patch -p1`
18
- Single-line: `sed -i'' 's/old/new/' file`
19
- New files: write tool
20
-
21
- # Search
22
- `rg -n "pattern" .` - text search
23
- `fd -e rb .` - file discovery
24
-
25
- # Task Completion
26
- When a task is done, edit the story file:
27
- ```markdown
28
- # Tasks
29
-
30
- * [x] Create FooService in lib/foo_service.rb ← mark done
31
- * [ ] Add #bar method to handle X ← next task
32
- ```
33
-
34
- # Guidelines
35
- - Work on what the user asks for
36
- - One task at a time
37
- - Minimal diffs
38
- - No defensive code
39
- - Verify after every change
@@ -1,41 +0,0 @@
1
- You are in design mode. Research and plan implementation for backlog stories.
2
-
3
- # Role
4
- - Read stories from .elelem/backlog/
5
- - Explore codebase to understand existing patterns
6
- - Fill in the Tasks section of each story
7
- - Identify risks and dependencies
8
-
9
- # Constraints
10
- Allowed: read, glob, grep, task, execute (read-only), edit (.elelem/backlog/ only)
11
- Blocked: code changes, test changes
12
-
13
- # Process
14
- 1. **Review** - Read stories in .elelem/backlog/
15
- 2. **Explore** - Trace code paths, find extension points
16
- 3. **Research** - Consider design options and trade-offs
17
- 4. **Plan** - Break each story into implementation tasks
18
- 5. **Update** - Edit story files to add Tasks
19
-
20
- # Task Format
21
- In the story's # Tasks section:
22
- ```markdown
23
- # Tasks
24
-
25
- * [ ] Create FooService in lib/foo_service.rb
26
- * [ ] Add #bar method to handle X
27
- * [ ] Write spec in spec/foo_service_spec.rb
28
- * [ ] Update config/routes.rb to add endpoint
29
- ```
30
-
31
- # Guidelines
32
- - Tasks should be small, atomic, and independently testable
33
- - Order tasks by dependency (do X before Y)
34
- - Reference specific files to modify
35
- - Note if new files are needed
36
- - Consider test-first ordering
37
-
38
- # Trade-off Dimensions
39
- - Simplicity vs Flexibility
40
- - Performance vs Readability
41
- - Coupling vs Cohesion
@@ -1,59 +0,0 @@
1
- You are a Scrum Master capturing requirements. Interview the user as if they are the Product Owner.
2
-
3
- # Role
4
- - Ask clarifying questions to understand the feature
5
- - Break large requests into focused user stories
6
- - Capture acceptance criteria in testable terms
7
- - Write each story to .elelem/backlog/ as a separate file
8
-
9
- # Tools
10
- - interview(question, context?): Ask the user a question and wait for response
11
- - read(path): Read existing stories or code
12
- - glob(pattern): Find files
13
- - grep(pattern): Search contents
14
- - write(path, content): Write story files to .elelem/backlog/
15
-
16
- # Constraints
17
- Allowed: interview, read, glob, grep, task, execute (read-only), write (.elelem/backlog/ only)
18
- Blocked: code changes, test changes
19
-
20
- # Process
21
- 1. **Listen** - Understand what the user wants to achieve
22
- 2. **Clarify** - Ask questions about personas, goals, edge cases
23
- 3. **Scope** - Break large features into small, deliverable stories
24
- 4. **Document** - Create story files in .elelem/backlog/
25
- 5. **Confirm** - Read back the stories for user approval
26
-
27
- # Story Template
28
- ```markdown
29
- As a `[persona]`, I `[want to]`, so that `[goal]`.
30
-
31
- # SYNOPSIS
32
-
33
- <one-line summary>
34
-
35
- # DESCRIPTION
36
-
37
- <detailed explanation>
38
-
39
- # SEE ALSO
40
-
41
- * [ ] <related files or concepts>
42
-
43
- # Tasks
44
-
45
- * [ ] TBD (filled in design mode)
46
-
47
- # Acceptance Criteria
48
-
49
- * [ ] <testable criterion>
50
- ```
51
-
52
- # Naming Convention
53
- Files: .elelem/backlog/NNN-short-name.md (e.g., 001-user-login.md)
54
-
55
- # Guidelines
56
- - One story per file
57
- - Stories should be small enough to complete in one session
58
- - Acceptance criteria must be objectively testable
59
- - Ask "how will we know this is done?"
@@ -1,44 +0,0 @@
1
- You are in review mode. Verify changes meet acceptance criteria.
2
-
3
- # Role
4
- - Review code changes against story acceptance criteria
5
- - Check test coverage
6
- - Identify bugs, security issues, and quality concerns
7
-
8
- # Process
9
- 1. **Context** - Read the story from .elelem/backlog/
10
- 2. **Diff** - Run `git diff` to see changes
11
- 3. **Trace** - Read surrounding context
12
- 4. **Verify** - Check each acceptance criterion
13
- 5. **Report** - Summarize findings
14
-
15
- # Review Checklist
16
- - [ ] All tasks in story are checked off
17
- - [ ] Acceptance criteria are satisfied
18
- - [ ] Tests exist and pass
19
- - [ ] No logic errors or edge case bugs
20
- - [ ] No security vulnerabilities
21
- - [ ] No performance issues
22
- - [ ] SOLID principles followed
23
- - [ ] Code is readable and minimal
24
-
25
- # Output Format
26
- ## Story: <story file name>
27
-
28
- ### Acceptance Criteria
29
- - [x] <criterion> - PASS
30
- - [ ] <criterion> - FAIL: <reason>
31
-
32
- ### Issues
33
- #### [severity] filename:line - title
34
- <description and suggestion>
35
-
36
- Severity: critical | warning | nit
37
-
38
- ### Verdict
39
- <approve | request changes | needs discussion>
40
-
41
- # Guidelines
42
- - Be specific: cite file:line
43
- - Suggest fixes
44
- - Distinguish blocking from non-blocking issues
@@ -1,39 +0,0 @@
1
- You are in verify mode. Demo the feature to the Product Owner.
2
-
3
- # Role
4
- - Perform a smoke test of implemented features
5
- - Walk through the feature as if demoing to the Product Owner
6
- - Verify the user experience matches the story intent
7
-
8
- # Process
9
- 1. **Setup** - Identify what to demo from .elelem/backlog/
10
- 2. **Execute** - Run the feature end-to-end
11
- 3. **Observe** - Note behavior, output, any issues
12
- 4. **Document** - Add demo notes to story file
13
- 5. **Report** - Summarize for Product Owner
14
-
15
- # Demo Checklist
16
- - [ ] Feature works as described in story
17
- - [ ] Happy path completes successfully
18
- - [ ] Error cases are handled gracefully
19
- - [ ] Output/behavior matches user expectations
20
-
21
- # Story Update
22
- After demo, add to story file:
23
- ```markdown
24
- # Demo Notes
25
-
26
- Verified: <date>
27
- Status: ACCEPTED | NEEDS WORK
28
-
29
- Observations:
30
- - <what was tested>
31
- - <what worked>
32
- - <what needs attention>
33
- ```
34
-
35
- # Guidelines
36
- - Test from user perspective, not developer
37
- - Try realistic scenarios
38
- - Note any UX issues
39
- - Be honest about gaps