pradeepmouli/speckit-sync-apply
.agents/skills/speckit-sync-apply/SKILL.md
Apply approved drift resolutions to specs and/or code
$ install --global
skillsauthnpx skillsauth add pradeepmouli/lspeasy speckit-sync-applyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 7:59 AM4.7s1 file scanned
SKILL.md
- name:
- speckit-sync-apply
- description:
- Apply approved drift resolutions to specs and/or code
- compatibility:
- Requires spec-kit project structure with .specify/ directory
- author:
- github-spec-kit
- source:
- sync:commands/apply.md
Spec Sync: Apply Resolutions
Apply approved resolutions from the proposals file. Updates specs or generates implementation tasks.
User Input
$ARGUMENTS
Prerequisites
- Run
speckit.sync.analyzeto generate drift report - Run
speckit.sync.proposeto generate proposals - Review and mark proposals as approved in
.specify/sync/proposals.json
Context
Read:
.specify/sync/proposals.json- proposals with approval status- Original spec files that need updating
Steps
1. Load Approved Proposals
Read proposals and filter to those marked approved: true.
If no proposals are approved:
- In interactive mode: prompt to review proposals first
- In batch mode: exit with "No approved proposals to apply"
2. Apply Backfill Proposals
For each approved BACKFILL proposal:
- Read the original spec file
- Locate the requirement being updated
- Replace with proposed text
- Add any new acceptance scenarios
- Update the spec's "Status" or "Last Modified" metadata
- Write the updated spec
Track changes:
{
"spec": "spec-011",
"requirement": "FR-001",
"before": "original text",
"after": "updated text",
"applied_at": "timestamp"
}
3. Apply New Spec Proposals
For each approved NEW_SPEC proposal:
- Create new spec directory:
specs/{spec-id}/ - Write
spec.mdwith generated content - Create empty
tasks.mdplaceholder - Add to git (if in a git repo)
4. Generate Implementation Tasks for Align Proposals
For ALIGN proposals (spec → code), don't modify code directly. Instead:
- Generate a task file:
.specify/sync/align-tasks.md - Each task describes the code change needed
- Optionally create GitHub issues if
--create-issuesis passed
Task format:
## Task: Align [spec-id]/[requirement]
**Spec Requirement**: [FR-XXX]
**Current Code**: [description of current behavior]
**Required Change**: [description of needed change]
**Files to Modify**: [list of files]
**Estimated Effort**: [small/medium/large]
### Acceptance Criteria
- [ ] [criterion 1]
- [ ] [criterion 2]
5. Handle Supersede Resolutions
For SUPERSEDE proposals:
- Add
superseded_byfield to old spec metadata - Add cross-reference in new spec
- Optionally mark old spec as deprecated
6. Generate Apply Report
# Sync Apply Report
Applied: [timestamp]
## Changes Made
### Specs Updated
| Spec | Requirement | Change Type |
|------|-------------|-------------|
| spec-011 | FR-001 | Modified |
| spec-011 | FR-015 | Added |
### New Specs Created
- spec-013-reconciliation
### Implementation Tasks Generated
- 3 tasks in `.specify/sync/align-tasks.md`
### Not Applied
| Proposal | Reason |
|----------|--------|
| spec-008/FR-003 | Not approved |
## Next Steps
1. Review updated specs
2. Commit changes: `git add specs/ && git commit -m "sync: apply drift resolutions"`
3. Implement tasks in align-tasks.md
7. Save Report
Write to:
.specify/sync/apply-report.md.specify/sync/apply-report.json
Options
--dry-run: Show what would be applied without making changes--create-issues: Create GitHub issues for ALIGN tasks--auto-commit: Commit spec changes automatically--spec <id>: Apply only proposals for a specific spec
Example Usage
/speckit.sync.apply --dry-run
/speckit.sync.apply
/speckit.sync.apply --auto-commit --create-issues
Safety
- Always creates backups before modifying specs
- Backups stored in
.specify/sync/backups/ - Use
--dry-runfirst to preview changes - All changes are logged for audit
Related Skills
pradeepmouli/lsp-refactor
tools
VerifiedTrustedCommunity
Use for ANY rename, file-move, or move-symbol refactor — especially rename-heavy work across multiple files. Claude Code's built-in LSP tool is READ-ONLY (find references, but no rename / file-move / move-symbol). Hand-editing those refactors silently misses re-exports, aliased imports, type-only imports, and {@link} doc references. This skill drives a real language server via the `lspeasy` CLI to apply a correct WorkspaceEdit that catches every reference. Trigger when the user asks to rename a function/class/variable/type project-wide, move a file and fix its importers, or pull a symbol out into another module.
2SKILL.mdUpdated Jun 3, 2026
pradeepmouli/lspeasy-core
tools
VerifiedTrustedCommunity
Documentation site for lspeasy Use when: You are building a browser-based LSP client, a WebSocket-backed language....
2SKILL.mdUpdated Apr 17, 2026
pradeepmouli/lspeasy-client
tools
VerifiedTrustedCommunity
Documentation site for lspeasy Use when: You are implementing a custom client layer and need the same validation....
2SKILL.mdUpdated Apr 17, 2026
pradeepmouli/lspeasy
tools
VerifiedTrustedCommunity
Use when working with lspeasy (client, core, server). Covers: lsp, language-server-protocol, lsp-client, language-client, jsonrpc, transport, lsp-server, language-server.
1SKILL.mdUpdated Apr 25, 2026