integrate
starsforks
How to install integrate?
yha9806/academic-writing-toolkit/integrate
$npx -y skills add yha9806/academic-writing-toolkit --skill integrateMap reading notes to thesis chapters and integrate key arguments into the manuscript. Use after completing a reading session to weave new material into the thesis.
SKILL.md
| 1 | # /integrate — Thesis Integration Skill |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | After completing a reading session, this skill weaves key arguments, quotes, and concepts from reading notes into the thesis manuscript. It ensures new material is placed in the right chapter and section, with proper attribution and minimal disruption to existing structure. |
| 6 | |
| 7 | ## Trigger Words |
| 8 | |
| 9 | This skill activates on: `integrate`, `weave in`, `add to thesis`, `/integrate`. |
| 10 | |
| 11 | ## Workflow |
| 12 | |
| 13 | 1. **Scan the specified notes file(s)** for the `## Thesis Connections` table and `## Key Arguments` section. If the user does not specify which notes file, ask. If the user says "all pending", scan all notes files with `Status: completed` (not yet `integrated`). |
| 14 | |
| 15 | 2. **Read target chapter files** in `chapters/` to identify insertion points. Use Grep to find relevant sections, existing citations of the same author, and thematic paragraphs where the new material fits. |
| 16 | |
| 17 | 3. **Present an integration plan** as a table. Do not execute any changes yet. |
| 18 | |
| 19 | ``` |
| 20 | ## Integration Plan: {Author} -- {Title} |
| 21 | |
| 22 | | # | Source Concept | Chapter | Section | Insertion Type | Preview | |
| 23 | |---|---------------|---------|---------|----------------|---------| |
| 24 | | 1 | {concept} | Ch{N} | {section ref} | new paragraph / expand existing / add citation / add footnote | {first 10 words of proposed text} | |
| 25 | |
| 26 | Estimated word count delta: +{N} words across {N} chapters. |
| 27 | Proceed? (yes / edit plan / cancel) |
| 28 | ``` |
| 29 | |
| 30 | 4. **Wait for user approval.** The user may: |
| 31 | - Say "yes" or "proceed" to execute the plan as shown. |
| 32 | - Say "edit plan" and specify changes (remove a row, change a section, etc.). |
| 33 | - Say "cancel" to abort. |
| 34 | |
| 35 | 5. **Execute the integration.** For each row in the approved plan: |
| 36 | - Read the target chapter file. |
| 37 | - Use Edit to insert, expand, or add citations at the specified location. |
| 38 | - Preserve existing paragraph structure. Do not rewrite surrounding text. |
| 39 | |
| 40 | 6. **Update the notes file.** Change `Status` from `completed` to `integrated` using Edit. Update the `Last updated` timestamp. |
| 41 | |
| 42 | 7. **Report results.** |
| 43 | |
| 44 | ``` |
| 45 | ## Integration Complete |
| 46 | |
| 47 | | Chapter | Words before | Words after | Delta | |
| 48 | |---------|-------------|------------|-------| |
| 49 | | {ch} | {N} | {N} | +{N} | |
| 50 | |
| 51 | Total: +{N} words across {N} chapters. |
| 52 | Notes file status updated to: integrated. |
| 53 | ``` |
| 54 | |
| 55 | ## Insertion Types |
| 56 | |
| 57 | - **new paragraph**: Insert a new paragraph at the specified location. Include a topic sentence, the integrated content, and a transition. |
| 58 | - **expand existing**: Add sentences to an existing paragraph. Maintain the paragraph's flow and argument direction. |
| 59 | - **add citation**: Insert an inline citation (Author, Year) or a parenthetical reference to support an existing claim. |
| 60 | - **add footnote**: Add a footnote with extended discussion or a qualifying remark. |
| 61 | |
| 62 | ## Constraints |
| 63 | |
| 64 | 1. **Never integrate without showing the plan first.** The user must approve before any chapter file is modified. |
| 65 | 2. **Preserve existing chapter structure.** Do not reorder sections, delete content, or rewrite paragraphs beyond the insertion point. |
| 66 | 3. **Track and report word count changes** for every chapter affected. |
| 67 | 4. **Attribution**: Every integrated quote must include a page reference. Every integrated argument must cite the source. |
| 68 | 5. **No emoji** in output or inserted text. |
| 69 | 6. **British English** for all inserted text (e.g., "colour" not "color", "analyse" not "analyze"). |
| 70 | 7. **One notes file at a time** unless the user explicitly requests batch integration. |
People who liked this also viewed
6 picksType
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026
- code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026
- baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 2026
- code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 2026
- code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 2026
