SepineTam/mcp-for-stata / .claude/skills/rfc-impl-generator
rfc-impl-generator
VerifiedGenerate RFC and IMPL documents from a user-provided feature/fix description. Use when the user says something like "I want to add a feature with codex", "Implement this", "Write an RFC for...", or provides a short idea that needs to be formalized into the ai-driven/rfc + ai-driven/impl pipeline.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.3 KB |
| references/impl-example.md | markdown | 2.2 KB |
| references/impl-template.md | markdown | 617 B |
| references/rfc-example.md | markdown | 3.8 KB |
| references/rfc-template.md | markdown | 796 B |
| references/workflow-example.md | markdown | 4.7 KB |
references/impl-example.md
View on GitHub# IMPL Example: Unix do-file execution append clear before exit
```markdown
# IMPL: Unix do-file execution append clear before exit
## Summary
Insert a `clear` command before `exit, STATA` in the two Unix execution paths of `StataDo` to prevent Stata from hanging with r(4) when the in-memory dataset has been modified.
## Context
`StataDo` in `src/stata_mcp/stata/stata_do/do.py` has four execution methods:
- `_execute_unix_like` — macOS/Linux, no monitors
- `_execute_unix_like_with_monitors` — macOS/Linux, with monitors
- `_execute_windows` — Windows, no monitors
- `_execute_windows_with_monitors` — Windows, with monitors
Each constructs a multi-line commands string sent to Stata via `proc.communicate()`. The current Unix commands end with:
```
log close _all
exit, STATA
```
When a do-file modifies the dataset, `exit, STATA` triggers r(4) and the process hangs indefinitely because Stata prompts the user to save or specify `clear`.
## Suggested Plan
### Step 1: Modify `_execute_unix_like`
**File**: `src/stata_mcp/stata/stata_do/do.py`
SUGGESTED: In the `commands` f-string, add `clear` on a new line between `log close _all` and `exit, STATA`.
### Step 2: Modify `_execute_unix_like_with_monitors`
**File**: `src/stata_mcp/stata/stata_do/do.py`
SUGGESTED: Make the identical insertion in the monitored version's `commands` string.
### Step 3: Verify Windows paths unchanged
**File**: `src/stata_mcp/stata/stata_do/do.py`
SUGGESTED: Confirm neither `_execute_windows` nor `_execute_windows_with_monitors` was touched.
## Edge Cases
- Empty dataset after do-file: `clear` is harmless
- Do-file already contains `clear`: repeating it is safe
- User expects unsaved data to persist: not applicable — MCP execution is stateless and the dataset was never meant to be kept in memory across calls
## Checking List
- [ ] `_execute_unix_like` commands include `clear` before `exit, STATA`
- [ ] `_execute_unix_like_with_monitors` commands include `clear` before `exit, STATA`
- [ ] `_execute_windows` and `_execute_windows_with_monitors` unchanged
- [ ] `execute_dofile` method signature unchanged
- [ ] Test do-file that modifies data no longer hangs
- [ ] Test read-only do-file still works normally
- [ ] Lint check passes
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |