armelhbobdad/oh-my-skills / _bmad/skf/skf-update-skill
skf-update-skill
VerifiedSmart regeneration preserving [MANUAL] sections after source changes. Use when the user requests to "update a skill" or "regenerate a skill."
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.8 KB |
| customize.toml | config | 2.8 KB |
| references/detect-changes.md | markdown | 48.1 KB |
| references/gap-driven.md | markdown | 54.2 KB |
| references/health-check.md | markdown | 4.3 KB |
| references/init.md | markdown | 45.7 KB |
| references/invocation-contract.md | markdown | 4.0 KB |
| references/manual-section-rules.md | markdown | 1.2 KB |
| references/merge.md | markdown | 36.0 KB |
| references/re-extract.md | markdown | 14.9 KB |
| references/report.md | markdown | 27.8 KB |
| references/write.md | markdown | 78.8 KB |
| scripts/skf-new-file-diff.py | script | 12.4 KB |
customize.toml
View on GitHub# DO NOT EDIT -- overwritten on every update.
#
# Workflow customization surface for skf-update-skill.
# Team overrides: {project-root}/_bmad/custom/skf-update-skill.toml
# Personal overrides: {project-root}/_bmad/custom/skf-update-skill.user.toml
[workflow]
# --- Configurable below. Overrides merge per BMad structural rules: ---
# scalars: override wins • arrays (persistent_facts, activation_steps_*): append
# arrays-of-tables with `code`/`id`: replace matching items, append new ones.
# Steps SKILL.md On Activation step 4 runs once this file resolves: after
# the config load, the headless flag and the run folder, before
# activation_steps_append and references/init.md. Overrides append. Use for
# org-wide pre-flight checks (auth, network, compliance) that must precede
# any skill update work.
activation_steps_prepend = []
# Steps to run after activation, before references/init.md (the first
# stage) runs. Overrides append. Use for context loads or banner
# customization that should run once activation completes successfully.
activation_steps_append = []
# Persistent facts the workflow keeps in mind for the whole run
# (drift policies, manual-section preservation rules, compliance
# guardrails). Overrides append.
#
# Each entry is one of:
# - a literal sentence, e.g. "Updates must preserve [MANUAL] sections verbatim."
# - a file reference prefixed with `file:`, e.g.
# "file:{project-root}/docs/update-policy.md" (globs supported; file
# contents are loaded and treated as facts).
# - an entry prefixed with `!`, which loads nothing and drops each earlier
# entry it names.
#
# The default below loads every project-context.md under {project-root}.
# Overrides append, so they cannot delete it; to stop loading those files,
# set in {project-root}/_bmad/custom/skf-update-skill.toml:
# persistent_facts = ["!file:{project-root}/**/project-context.md"]
persistent_facts = [
"file:{project-root}/**/project-context.md",
]
# Pipeline-integration hook invoked after report.md §5b writes the result
# contract (the per-run record plus update-skill-result-latest.json) of a
# finished run: an update that wrote a version, or a run that found no
# change (its result files go in the current version's forge folder). The
# command is called as:
# <on_complete> --result-path=<{forge_version}/update-skill-result-latest.json>
# It is not called for --detect-only or --dry-run, which write no result
# file, nor when a run halts or did not write its -latest copy.
# Useful for Slack notifications, dashboard ingest, CI hooks, or chaining a
# downstream skill (audit, export, test). A failure is reported to the user
# in one line and never fails the workflow; it does not reach the result
# files or the SKF_UPDATE_RESULT_JSON line, which are written before the
# hook runs.
#
# Empty string = no-op (default).
on_complete = ""
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |