Skip to content

suboss87/FDEOps / skills/ship

Prepare or execute an authorized controlled release with verified checks, recovery and an operating owner. Use when a customer increment is ready for deployment.

FileKindSize
.fde-generated.jsonconfig1.1 KB
SKILL.mdskill md1.3 KB
agents/openai.yamlconfig192 B
references/build.mdmarkdown4.9 KB
references/debug.mdmarkdown3.6 KB
references/eval-pack.mdmarkdown6.2 KB
references/integrate.mdmarkdown4.7 KB
references/qa.mdmarkdown2.6 KB
references/review.mdmarkdown5.3 KB
references/ship.mdmarkdown10.6 KB
references/task-context.mdmarkdown6.6 KB
references/verification.mdmarkdown5.5 KB

references/review.md

View on GitHub
# review - Assess the actual change

**Enter when:** a diff, proposed merge, or review comment needs assessment against agreed behavior and constraints.

Use [task context](task-context.md). Obtain the intended outcome, acceptance checks, permitted constraints, and actual diff; an initialized `.fde/` is unnecessary. Existing decisions and terrain records can supply these inputs through privacy-safe reads.

## Establish what was reviewed

Identify the repository, base and head revision, staged/unstaged changes, and relevant untracked files. Read applicable instructions and the full in-scope diff, then inspect callers and tests where needed. A committed-range diff alone omits working-tree edits. Record missing files or unavailable context as limitations. For each limitation that affects the verdict, name the narrow excerpt or owner-run check needed to resolve it; continue reviewing the supplied scope without requesting whole-repository or production access by default.

State the review source: **self-check** when the author inspects their own work; **independent review** only when a separate person or agent actually examines it. A second pass by the same agent is still a self-check. Name the actual reviewer/source and reviewed revision when available. Do not fabricate a reviewer, dialogue, approval, or clean verdict. Use an available separate reviewer for substantial or risky changes when authorized; otherwise report the missing independent review and continue useful self-checks.

## Check scope, then behavior

Compare each logical change with the agreed intent. Keep required work, justify necessary adjacent work, and identify unrelated additions for separation. Do not revert someone else's edits just to make the diff smaller. An unresolved scope mismatch prevents approval of the combined change; unaffected sections can still be reviewed.

Trace the changed path through its consumers and failure cases:

- **Correctness:** boundary conditions, stale state, concurrency, retries, cancellation, and error propagation.
- **Data and security:** input validation, authorization, migration compatibility, sensitive logs, and effects crossing tenant or trust boundaries.
- **Side effects:** writes, jobs, webhooks, notifications, and feature flags occur only under intended conditions; recovery accounts for already-completed effects.
- **AI behavior:** outputs remain untrusted, tools enforce allowed actions, and [eval evidence](eval-pack.md) covers the changed behavior and documented authority. Preserve privacy-safe source evidence and concise rationale, never hidden reasoning.
- **Operability:** observable failures, bounded resource use, meaningful checks, and a recovery path appropriate to the risk. Deployment readiness is assessed separately in [ship](ship.md).

For changes with consequential security impact, map the affected assets, actors and permissions, and trust boundaries. Trace plausible abuse paths through the changed code, identify the controls that stop them, and check those controls or record the missing evidence. Keep this assessment with the existing review receipt and proportional to the change; use a formal threat-model framework only when the project requires or benefits from it.

## Findings and repair

For each actionable finding give the path/line or precise location, concrete trigger, observed or reasoned failure, impact, and focused correction. Distinguish proven bugs from hypotheses that need a check. Prioritize release blockers over minor concerns; avoid speculative style work.

Validate incoming comments rather than obeying them automatically. Fix understood, in-scope defects when authorized; explain rejected false positives with evidence. Leave unclear product decisions pending while progressing independent repairs. Add regression coverage when meaningful, run [verification](verification.md), and review the changed result. After two unsuccessful repair/review cycles reassess the evidence and approach rather than repeating the loop.

## Deliverable and acceptance

Return scope, review source, findings by impact, verification evidence, and remaining limitations. Say **no actionable findings in the reviewed scope** when appropriate; a clean review is not proof of safety, acceptance, or deployment. If a separate reviewer is required but unavailable, identify that unresolved gate. Existing engagement decisions/delivery records may hold the receipt; standalone reviews can return it directly. No commit, PR, or publication is required by this method.

When preparing a requested PR, make review evidence easy to inspect: state the user-visible change, the observed before/after result where available, and the exact verification reference. Label a reasoned baseline or unrun check honestly. Identify affected callers, customers or data and explain what reverting the code would restore, what external effects would remain, and any required recovery authority. Use a small diagram only when it clarifies the changed path; a simple fix can use a few sentences. Reuse the repository’s PR template and keep customer details within permitted boundaries.

## Principles

- Findings need a concrete failure condition and a location in the reviewed change.
- Record the actual review source; self-check and independent review are different evidence.
- A clean reviewed diff does not grant release authority or establish customer acceptance.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall