메뉴
Generate PR documentation from completed spec and git diff. Use when: pr docs, generate docs, pull request docs, baldrick docs. Triggers on: pr docs, generate docs, document changes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Execute Baldrick iterations on existing specs. Use when: run baldrick, execute specs, implement features, start working. Triggers on: baldrick run, run specs, implement, execute features.
Iteratively improve test coverage until target is reached. Use when: improve coverage, test coverage, coverage target, baldrick coverage. Triggers on: coverage, test coverage, coverage loop.
Iteratively reduce code entropy by fixing smells and improving quality. Use when: cleanup, code smells, entropy, refactor loop, baldrick entropy. Triggers on: entropy, cleanup, code smells, reduce entropy.
Iteratively fix all linting errors until clean. Use when: fix lint, lint errors, lint loop, baldrick lint-fix. Triggers on: lint, fix lint, lint errors, lint loop.
Create a feature specification for Baldrick. Use when: create a spec, new feature, write spec for, plan this feature. Triggers on: create spec, baldrick create, new spec, feature spec.
Create comprehensive spec with diagrams, flows, and thorough documentation. Use when: detailed spec, comprehensive spec, full spec, baldrick spec. Triggers on: detailed, comprehensive, full spec, thorough.
| name | pr-docs |
| description | Generate PR documentation from completed spec and git diff. Use when: pr docs, generate docs, pull request docs, baldrick docs. Triggers on: pr docs, generate docs, document changes. |
Generate PR-ready documentation from a completed spec and git changes.
Philosophy: Clear documentation makes reviews faster and preserves context.
specs/[name].mddocs/[name]-changes.md# [Feature Name]
## Summary
Brief description of what was implemented.
## Changes
### Files Modified
- `path/to/file.ts` - What changed and why
- `path/to/other.ts` - What changed and why
### Files Added
- `path/to/new-file.ts` - Purpose of new file
## Implementation Details
### Key Decisions
- Decision 1 and rationale
- Decision 2 and rationale
### Trade-offs
- Trade-off considered and why this approach was chosen
## BDD Coverage
| Scenario | Status |
|----------|--------|
| Happy path login | ✅ Implemented |
| Invalid email | ✅ Implemented |
| Wrong password | ✅ Implemented |
## Testing
- [ ] Unit tests added
- [ ] Integration tests added
- [ ] Manual testing steps
## Screenshots/Examples
(If applicable - UI changes, API responses, etc.)
## Related
- Spec: `specs/[name].md`
- Related PRs: (if any)
User: "Generate PR docs for the login feature"
Output saved to: docs/login-changes.md
.md)docs/[spec-name]-changes.mddocs/[name]-changes.md