feat(skills): add compound-engineering implementation reference#1
Merged
Conversation
Adds skills/compound-engineering with references for recurring stack-specific breakages so workflow commands can consume fix recipes directly. Co-authored-by: Hermes <hermes@nousresearch.com>
Reviewer's GuideAdds a new compound-engineering skill with an implementation reference index and detailed markdown references for wagmi v7 migration and a specific Polymarket dashboard repair session, so workflow commands can consume concrete stack-specific fix recipes. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughThis PR introduces a new documentation skill system for compound engineering workflows. It adds a skill definition file that references two implementation guides: a comprehensive wagmi v6→v7 and viem v1→v2 migration reference with code patterns and troubleshooting, and session notes documenting fixes applied to the Polymarket Auto Dashboard. ChangesCompound Engineering Skill Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Analysis CompleteGenerated ECC bundle from 1 commits | Confidence: 50% View Pull Request #2Repository Profile
Changed Files (3)
Top hotspots
Top directories
Analysis Depth Readiness (commit-history, 7%)ECC Tools uses this to decide whether recommendations should stay at commit-history/setup guidance or expand into CI, security, harness, reference-set, AI-routing, and team backlog work.
Reference Set Readiness (0/7, 0%)
Likely Future Issues (2)
Suggested Follow-up Work (2)
Copy-ready bodies analysis: add reference-set evidence for skills/compound-engineering/SKILL.md + skills/compound-engineering/references/polymarket-auto-2026-05-09.md ## Summary
- Add reference-set or eval evidence for the recently changed AI, analyzer, skill, agent, command, or harness guidance surface.
## Why
- Backfill eval, golden trace, benchmark, or reference-set evidence before another AI or harness-analysis change lands on the touched surface.
## Touched paths
- `skills/compound-engineering/SKILL.md`
- `skills/compound-engineering/references/polymarket-auto-2026-05-09.md`
## Validation
- Add or update an eval, golden trace, benchmark, fixture, or reference-set artifact for the changed AI/harness behavior.
- Compare the changed behavior against the maintained reference set and record the pass/fail evidence.
- Confirm the follow-up evidence covers the same analyzer, skill, agent, command, or harness surface touched by this PR.skills: add quality evidence for skills/compound-engineering/SKILL.md + skills/compound-engineering/references/polymarket-auto-2026-05-09.md ## Summary
- Add skill-quality evidence for the recently changed skill, agent, command, or rule guidance.
## Why
- Backfill examples, validator, eval, or reference evidence before another skill or agent guidance change lands on the touched surface.
## Touched paths
- `skills/compound-engineering/SKILL.md`
- `skills/compound-engineering/references/polymarket-auto-2026-05-09.md`
## Validation
- Add or update examples, trigger coverage, frontmatter validation, or skill validator fixtures for the changed guidance.
- Run the relevant skill, agent, command, or rule validation flow and record pass/fail evidence.
- Confirm the follow-up evidence covers the same guidance surface touched by this PR.Generated Instincts (16)
After merging, import with: Files
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've found 2 issues
Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments
### Comment 1
<location path="skills/compound-engineering/SKILL.md" line_range="3" />
<code_context>
+---
+name: compound-engineering
+description: Implementation reference library for compound engineering workflows. For workflow orchestration, use slash commands under `commands/workflows/` (constitution, plan, work, review, compound). This skill provides stack-specific fix recipes those workflows consume.
+version: 1.0.0
+tags: [reference, fixes, typescript, react, nextjs, wagmi, automation]
</code_context>
<issue_to_address>
**suggestion (typo):** Consider inserting 'that' for smoother grammar in the final sentence of the description.
The clause "stack-specific fix recipes those workflows consume" is grammatically awkward. Please add "that" after "recipes" to read "stack-specific fix recipes that those workflows consume" for clearer documentation.
```suggestion
description: Implementation reference library for compound engineering workflows. For workflow orchestration, use slash commands under `commands/workflows/` (constitution, plan, work, review, compound). This skill provides stack-specific fix recipes that those workflows consume.
```
</issue_to_address>
### Comment 2
<location path="skills/compound-engineering/SKILL.md" line_range="17" />
<code_context>
+
+# Compound Engineering — Implementation Reference
+
+Actionable fix recipes for recurring breakages. Use alongside `aegntic/compound-engineering` workflow commands.
+
+## Usage
</code_context>
<issue_to_address>
**issue (typo):** The identifier `aegntic/compound-engineering` likely contains a typo.
If this is meant to reference the repository, please change it to `agentic/compound-engineering` to avoid confusion.
```suggestion
Actionable fix recipes for recurring breakages. Use alongside `agentic/compound-engineering` workflow commands.
```
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
| @@ -0,0 +1,40 @@ | |||
| --- | |||
| name: compound-engineering | |||
| description: Implementation reference library for compound engineering workflows. For workflow orchestration, use slash commands under `commands/workflows/` (constitution, plan, work, review, compound). This skill provides stack-specific fix recipes those workflows consume. | |||
There was a problem hiding this comment.
suggestion (typo): Consider inserting 'that' for smoother grammar in the final sentence of the description.
The clause "stack-specific fix recipes those workflows consume" is grammatically awkward. Please add "that" after "recipes" to read "stack-specific fix recipes that those workflows consume" for clearer documentation.
Suggested change
| description: Implementation reference library for compound engineering workflows. For workflow orchestration, use slash commands under `commands/workflows/` (constitution, plan, work, review, compound). This skill provides stack-specific fix recipes those workflows consume. | |
| description: Implementation reference library for compound engineering workflows. For workflow orchestration, use slash commands under `commands/workflows/` (constitution, plan, work, review, compound). This skill provides stack-specific fix recipes that those workflows consume. |
|
|
||
| # Compound Engineering — Implementation Reference | ||
|
|
||
| Actionable fix recipes for recurring breakages. Use alongside `aegntic/compound-engineering` workflow commands. |
There was a problem hiding this comment.
issue (typo): The identifier aegntic/compound-engineering likely contains a typo.
If this is meant to reference the repository, please change it to agentic/compound-engineering to avoid confusion.
Suggested change
| Actionable fix recipes for recurring breakages. Use alongside `aegntic/compound-engineering` workflow commands. | |
| Actionable fix recipes for recurring breakages. Use alongside `agentic/compound-engineering` workflow commands. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
skills/compound-engineeringwith references for recurring stack-specific breakages so workflow commands can consume fix recipes directly.What's new
skills/compound-engineering/SKILL.md— routing index mapping workflow phases to reference filesreferences/wagmi-v7-migration.md— v6→v7 migration patterns, ABI tuples, balance APIs, viem v2 rewritereferences/polymarket-auto-2026-05-09.md— 60+ TS fixes, runtime crash resolutions, production verification logsWhy
Local Hermes compound-engineering skill had actionable stack recipes that weren't surfaced into the workflow repo. This bridges
commands/workflows/*execution with the implementation details those workflows actually hit.Co-authored-by: Hermes hermes@nousresearch.com
Summary by Sourcery
Add a compound-engineering skill that documents stack-specific fix recipes and session notes for recurring frontend and wagmi/viem issues.
Documentation:
Summary by CodeRabbit