kramme-cc-workflow/skills/kramme:hooks:configure-links/SKILL.md
Configure the context-links hook by updating hooks/context-links.config with workspace, team key, and issue regex overrides. Use when end users want to set up or change context-links behavior without manually editing files.
npx skillsauth add abildtoft/kramme-cc-workflow kramme:hooks:configure-linksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Configure the context-links hook using a local config file.
${CONTEXT_LINKS_CONFIG_FILE:-${CLAUDE_PLUGIN_ROOT}/hooks/context-links.config} — resolve this once and use the result as the target for every read, write, and delete below (referred to as "the config file"). Honor the CONTEXT_LINKS_CONFIG_FILE override: the hook reads from this same resolved path, so editing any other path has no effect.${CLAUDE_PLUGIN_ROOT}/hooks/context-links.config.exampleDo not use this skill to enable or disable the hook itself (that is the hook toggle system), or to edit any other hook.
CONTEXT_LINKS_LINEAR_WORKSPACE_SLUGCONTEXT_LINKS_LINEAR_TEAM_KEYSCONTEXT_LINKS_LINEAR_ISSUE_REGEX/kramme:hooks:configure-links:
/kramme:hooks:configure-links show:
CONTEXT_LINKS_* env vars, legacy LINEAR_* env vars, then the built-in defaults in hooks/context-links.sh. Do not present a config-file value as the final value when an env var may override it./kramme:hooks:configure-links reset:
hooks/context-links.sh/kramme:hooks:configure-links KEY=VALUE [KEY=VALUE ...]:
$ARGUMENTS by spaces.show and reset are mutually exclusive: reject if both appear, or if either appears alongside any KEY=VALUE token.= as KEY=VALUE updates.show nor reset and contains no =, with a clear message listing the supported keys.CONTEXT_LINKS_LINEAR_TEAM_KEYS, use commas: ENG,OPS,PLAT..example.KEY=VALUE, edit by reading the file, modifying it in memory, and writing it back. Do not use sed: its replacement breaks on regex/metacharacter values such as (ENG|OPS|PLAT)-[0-9]+.
KEY="VALUE", wrapping it in double quotes and escaping any embedded " and \.KEY="VALUE".KEY="VALUE" at the end of the file.If no arguments are provided:
show behavior first.KEY=VALUE format (or blank to cancel).reset, after deletion, report that the hook will use its built-in defaults from hooks/context-links.sh./kramme:hooks:configure-links show
/kramme:hooks:configure-links CONTEXT_LINKS_LINEAR_WORKSPACE_SLUG=acme
/kramme:hooks:configure-links CONTEXT_LINKS_LINEAR_TEAM_KEYS=ENG,OPS,PLAT
/kramme:hooks:configure-links reset
development
One-way migration of a local SIW project into Linear. Creates one Linear project, migrates the main spec and supporting specs as Linear Documents, creates milestones from SIW phases and issues from SIW issues, then prompts to retire the local siw/ files via /kramme:siw:remove. Linear becomes the source of truth; this is not a two-way sync and keeps no rerun mapping, so re-running can duplicate issues. Use when moving a planned SIW initiative into Linear for good. Not for implementing issues, defining new SIW issues, or generating an issue breakdown.
development
Compare an existing PR's title and body against the actual branch diff and report drift — false claims, missing major changes, stale scope, missing risk callouts. Use after pushing changes to a branch with an open PR, or before requesting review. Read-only by default; add --fix to delegate to kramme:pr:generate-description for an updated description. Complements kramme:pr:code-review (which checks description accuracy as one signal among many code-quality checks) by being a fast, focused, single-purpose check that runs in seconds.
tools
Reviews plugin skills for focused scope, progressive disclosure, portability, safety, retry behavior, and documentation quality. Use when auditing a SKILL.md, skill directory, or proposed skill text against skill-authoring standards. Not for creating new skills, editing skills, or reviewing ordinary application code.
tools
Reviews recent agent session transcripts to find repeated manual workflows or repeated user asks, then proposes and optionally scaffolds only useful new skills or custom subagents. Use when the user asks to inspect recent sessions, find automation opportunities, or create reusable workflows from repeated work. Not for summarizing one session, general retrospectives, or codebase refactoring.