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…
@cowork-osInstall SkillProductivity
Skill
/extract-todos
Find all TODO/FIXME comments in codebase
Claude Code
$ npx -y skills add CoWork-OS/CoWork-OS --skill extract-todos --agent claude-code
Codex
$ npx skills add CoWork-OS/CoWork-OS --skill extract-todos -a codex -y
Cursor
$ npx skills add CoWork-OS/CoWork-OS --skill extract-todos -a cursor -y
Gemini CLI
$ npx skills add CoWork-OS/CoWork-OS --skill extract-todos -a gemini-cli -y
GitHub Copilot
$ npx skills add CoWork-OS/CoWork-OS --skill extract-todos -a github-copilot -y
OpenCode
$ npx skills add CoWork-OS/CoWork-OS --skill extract-todos -a opencode -y
Windsurf
$ npx skills add CoWork-OS/CoWork-OS --skill extract-todos -a windsurf -y
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`.
Stats
542
Stars
100
Forks
Active
Maintenance
TypeScript
Language
MIT
License
Last commit
Created
544157 skills
Stars on GitHub
Momentum
- stars in total
- 544
Other skills on cowork-os.
@cowork-osInstall Skilldeep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated…
@cowork-osInstall Skillfinding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate…
@cowork-osInstall Skillfix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger…
@cowork-osInstall Skillsecurity-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…
@cowork-osInstall Skillsecurity-scan
Use when the user asks for a repository-wide or scoped-path security scan.
@cowork-osInstall SkillMore skills from other plugins.
i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…
@ayghriInstall Skill
distilly
Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…
@titanwingsInstall SkillQuestions about extract-todos.
- Which coding agents can use extract-todos?
- extract-todos installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.