Skip to content

existential-birds/beagle / plugins/beagle-core/skills/receive-feedback

receive-feedback

Verified

Process external code review feedback with technical rigor. Use when receiving feedback from another LLM, human reviewer, or CI tool. Verifies claims before implementing, tracks disposition.

FileKindSize
EVALUATION.mdmarkdown3.2 KB
RESPONSE.mdmarkdown3.1 KB
SKILL.mdskill md10.9 KB
VERIFICATION.mdmarkdown2.5 KB
references/skill-integration.mdmarkdown1.7 KB

references/skill-integration.md

View on GitHub
# Skill Integration

## Using Code-Review Skills for Verification

When feedback relates to a specific technology, load the relevant skill
to verify against established codebase patterns.

## Skill Lookup Table

| Feedback Domain | Skill | Key Patterns to Check |
|-----------------|-------|----------------------|
| Python code quality | python-code-review | Type hints, error handling, naming |
| FastAPI endpoints | fastapi-code-review | Dependency injection, response models |
| SQLAlchemy models | sqlalchemy-code-review | Relationships, session handling |
| Pytest tests | pytest-code-review | Fixtures, parametrization, mocking |
| PostgreSQL queries | postgres-code-review | Indexes, joins, transactions |
| React components | shadcn-code-review | Component composition, accessibility |
| React Router | react-router-code-review | Loaders, actions, error boundaries |
| Tailwind styling | tailwind-v4 | Utility classes, responsive design |
| State management | zustand-state | Store structure, selectors |
| Vitest tests | vitest-testing | Test structure, mocking |

## Integration Workflow

1. **Identify domain** - What technology does the feedback concern?
2. **Load skill** - Load the matching `<skill-name>` skill from the relevant beagle plugin
3. **Cross-reference** - Does feedback align with skill guidance?
4. **Resolve conflicts** - If feedback contradicts skill, flag for discussion

## Conflict Resolution

If reviewer feedback conflicts with skill guidance:

```
Skill says: [pattern from skill]
Reviewer says: [contradicting suggestion]

Flag: "Feedback conflicts with established pattern. Discuss before implementing."
```

Codebase patterns (captured in skills) take precedence over external opinions.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall