Skill
attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and…
@cowork-osView SkillProductivity
Skill
/extract-todos
Find all TODO/FIXME comments in codebase
Install
$ npx -y skills add CoWork-OS/CoWork-OS --skill extract-todos --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/extract-todos
Context preview
The summary Claude sees to decide when to auto-load this skill.
Find all TODO/FIXME comments in codebase
SKILL.md
extract-todos.SKILL.mdname: extract-todos
description: "Find all TODO/FIXME comments in codebase"
version: "1.0.0"
metadata:
author: CoWork OS Contributors <info@coworkosapp.com>
Extract TODOs
Purpose
Find all TODO/FIXME comments in codebase
Routing
- Use when: Use when the user wants TODO/FIXME/HACK/XXX inventorying, triage, or stale-task cleanup.
- Do not use when: Don't use for implementation requests or when a code review already includes a TODO pass.
- Outputs: Prioritized TODO inventory with counts, file grouping, and stale candidates.
- Success criteria: Findings list all TODO-like markers with location, context, and suggested priority rationale.
Trigger Examples
Positive
- Use the extract-todos skill for this request.
- Help me with extract todos.
- Use when the user wants TODO/FIXME/HACK/XXX inventorying, triage, or stale-task cleanup.
- Extract TODOs: provide an actionable result.
Negative
- Don't use for implementation requests or when a code review already includes a TODO pass.
- Do not use extract-todos for unrelated requests.
- This request is outside extract todos scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | path | string | Yes | Path to search |
Runtime Prompt
- Current runtime prompt length: 517 characters.
- Runtime prompt is defined directly in `../extract-todos.json`.
Read more
name: extract-todos description: "Find all TODO/FIXME comments in codebase" version: "1.0.0" metadata: author: CoWork OS Contributors <info@coworkosapp.com>
Extract TODOs
Purpose
Find all TODO/FIXME comments in codebase
Routing
- Use when: Use when the user wants TODO/FIXME/HACK/XXX inventorying, triage, or stale-task cleanup.
- Do not use when: Don't use for implementation requests or when a code review already includes a TODO pass.
- Outputs: Prioritized TODO inventory with counts, file grouping, and stale candidates.
- Success criteria: Findings list all TODO-like markers with location, context, and suggested priority rationale.
Trigger Examples
Positive
- Use the extract-todos skill for this request.
- Help me with extract todos.
- Use when the user wants TODO/FIXME/HACK/XXX inventorying, triage, or stale-task cleanup.
- Extract TODOs: provide an actionable result.
Negative
- Don't use for implementation requests or when a code review already includes a TODO pass.
- Do not use extract-todos for unrelated requests.
- This request is outside extract todos scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | path | string | Yes | Path to search |
Runtime Prompt
- Current runtime prompt length: 517 characters.
- Runtime prompt is defined directly in `../extract-todos.json`.
Ships withcowork-os
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Get the whole plugin
Stats
450
Stars
77
Forks
Active
Maintenance
TypeScript
Language
MIT
License
4d ago
Last commit
7mo ago
Created
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
@cowork-osView SkillSkill
deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide…
@cowork-osView SkillSkill
finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository…
@cowork-osView SkillSkill
fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch,…
@cowork-osView SkillSkill
security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
@cowork-osView SkillSkill
security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
@cowork-osView Skill