skills/resume-rewrite/SKILL.md
Rewrite a resume using only the candidate's existing material, but only after a `resume-critic` review has been completed for a specific job description or job title. Use when the user wants the resume rewritten, tightened, or retargeted without inventing new experiences.
npx skillsauth add harshitsinghbhandari/domain-expansion resume-rewriteInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A resume rewriting workflow that converts resume-critic findings into a sharper, targeted resume using only the material already present in the resume and directly supported supporting notes.
Use this skill when the user wants the current resume rewritten for a specific job, but does not want invented experiences, fake metrics, or speculative new projects.
Good uses:
Bad uses:
resume-upgrade)resume-upgrade)This skill cannot start without a prior resume-critic output for the same resume and target job.
Before rewriting, require all three:
resume-critic for that same target jobIf the user has not run resume-critic, stop and ask for it first.
If the critique exists but targets a different job, do not reuse it. Run resume-critic again for the correct target first.
Rewrite only from existing material:
Do not invent:
Read:
resume-critic outputStart the framed brief with:
This rewrite is for: [full job title]Job description source: [pasted JD | linked JD | inferred from user-provided title only]Critique source: [resume-critic transcript/report reference or pasted output]From the resume-critic output, identify:
Produce an updated version of the resume that:
If there is not enough factual support to strengthen a claim honestly, leave it weaker rather than fabricating detail.
After the rewritten resume, provide:
resume-critic findings to the rewrite decisionsUse this exact structure:
## Job Target
This rewrite is for: [job title]
Job description source: [source]
## Resume-Critic Basis
[Short summary of the critique being acted on]
## Rewritten Resume
[Full rewritten resume]
## What Changed
[Concise explanation of the biggest rewrite choices]
## Missing Facts That Limited The Rewrite
[Only facts the user would need to provide for a stronger version]
resume-critic.resume-upgrade.development
Aggressive user-flow and boundary-bug analysis on a diff or branch. Auto-detects entry points, traces flows through changed code, finds every seam (cross-module calls, serialization, file I/O, shared state, schema versioning, network/IPC), and refuses to mark the work complete until each unverified boundary has a real round-trip test or an explicit written out-of-scope record persisted in an audit file. Use whenever the user says "boundary check", "seam check", "round-trip check", "flow boundaries", "user-flow check", "before merge", "is this safe to ship", "pre-merge gate", "boundary bugs", "verify the joins", or asks to validate cross-module joins, producer/consumer contracts, or end-to-end coverage of a change. Also use as a final gate from pr-review on any diff that touches more than one file, module, or process. Be pushy. Most surviving production bugs live at seams, not inside units — if the diff crosses any boundary, this skill almost certainly applies.
development
Run existing work through 5 specialist craftspeople who each produce an improved version, then peer-review and synthesize the best into a single improved artifact. Use when the user says "forge this", "improve this", "make this better", "level this up", "refine this", or asks for multi-angle improvement on code, copy, strategy, plans, designs, or any artifact where the current version works but could be significantly better. Do NOT use for decisions (use llm-council), simple edits, or creation from scratch.
development
Expert skill for maintaining a Keep a Changelog formatted CHANGELOG.md file. Use this skill whenever you add features, fix bugs, or release a new version. You MUST use this skill to record any changes that have a user-facing impact. It handles categorization (Added, Changed, Fixed, etc.), semantic versioning, and reverse-chronological ordering with surgical precision.
development
Comprehensive test suite audit that combines ruthless analysis with a solution-focused roadmap. Reads test suites (unit, integration, e2e) and source code, produces a brutal audit report of test quality and gaps, and generates prioritized testing improvements.