pedropacheco95
UserA codebase-understanding system for Claude Code: a persistent, actively-refreshed knowledge layer that makes Claude behave like it already knows your codebase.
Categories
Indexed Skills (34)
cortex-archive-ingest
Ingest a transcript, RFP, brief or contract into project memory. "add this to project memory".
cortex-extract-insight
Build, extract or refresh the codebase insight layer. "extract insight", "map this codebase".
cortex-register-tasks
Register or activate this project's cortex scheduled tasks in the Claude Desktop app.
specflow-bugs
Diagnose a bug to its root cause and file it. "X is broken", "why does X happen", test triage.
specflow-develop
Execute a plan into code, verified by tests. "implement this spec", "build this slice".
specflow-ingest
Reconcile an external document against the specs. "the client sent this", "ingest this".
specflow-lint
Check and fix spec-tree structure. "lint specs", "validate the spec tree".
specflow-new-project
Spec out a new project from scratch — two linked spec trees, overviews, build order. "new project", "start a new", "I want to build", or any product idea described before any code exists.
specflow-onboard-codebase
Reverse-engineer specs from existing code. "onboard this codebase".
specflow-spec-editor
Write spec files — create, edit, link. "update the spec", "add this criterion".
specflow-tests
Generate and run the four-layer test suite. "write tests", "generate tests from specs".
specflow-brainstorm
Turn a half-formed idea into an agreed spec. "I want to add X", "how should we approach".
specflow-entry
Classify every incoming user request against the project's spec tree (developer specs in `.specflow/specs/`, business specs in `.specflow/specs-business/`, and `_overview.md` folder docs) and route it to the correct action before any work begins. This skill is the mandatory entry point for ALL user interactions in a Specflow-managed project (any project with a `.specflow/specs/` directory, with or without a parallel `.specflow/specs-business/`). PROACTIVELY use this skill whenever the user says anything in a project under spec management — bug reports, feature requests, behavior changes, stakeholder questions, "what does this group do?", outcome/journey/metric talk, or anything that might touch a developer spec, a business spec, or a folder overview. Also triggers on "add a feature", "fix this bug", "change this behavior", "what does X do", "what's the goal of X", "why do we have X", and on requests that may have drifted between business and developer layers (e.g., a dev change that invalidates the business d
specflow-intent-reconcile
Pin a verbatim ask with an anchor test. "pin this ask", "did the spec keep it".
specflow-plan
Turn an agreed spec into an executable plan. "plan this", "break this down", "what are the steps".
specflow-receive-review
Verify review feedback before applying it. "here is the feedback".
specflow-request-review
Review a completed task diff for craft, anchored to its plan task and spec criterion. "review this", "review the diff", "code review". Correctness belongs to the tests, not to this review.
verification-before-completion
Evidence gate before claiming work done, fixed, or passing.
cortex-loop-bug-triage
Daily bug-ledger triage loop for a Cortex project. Use for the scheduled bug-triage task, or when the user says "run the bug-triage loop", "triage the open bugs", or "classify the bug ledger". Runs `cortex loop-bug-triage --collect`, classifies each worklist bug in-session with the specflow-bugs discipline, runs `cortex loop-bug-triage --report`, and summarises .cortex/pulse/reports/bug-triage.md.
cortex-loop-insight-refresh-daily
Daily insight-refresh loop for a Cortex project. Use for the scheduled insight-refresh-daily task, or when the user says "run the daily insight refresh", "refresh the insight layer", or "re-extract what changed". Runs `cortex loop-insight-refresh --daily --collect`, triages the uncertain files in-session, re-extracts L2/L3 via cortex-extract-insight in dirty-only mode, re-verifies stale references and aged edges, runs `cortex loop-insight-refresh --daily --apply`, and summarises .cortex/pulse/reports/insight-refresh.md.
cortex-loop-insight-refresh-full
Weekly ground-truth insight regeneration loop for a Cortex project. Use for the scheduled insight-refresh-full task, or when the user says "run the full insight refresh", "regenerate the insight graph", or "rebuild L4". Runs `cortex loop-insight-refresh --full --collect`, re-runs cross-scope L4 unification via cortex-extract-insight over all scopes, runs `cortex loop-insight-refresh --full --report`, and summarises .cortex/pulse/reports/insight-refresh.md.
cortex-loop-session-observe
Session-observation loop for a Cortex project — the v3 successor to v2's insight-gaps, and the primary producer of automatic, ungated project learning. Use for the scheduled session-observe task, or when the user says "run the session-observe loop", "what did we learn this session", or "capture session observations". Runs `cortex loop-session-observe --collect`, reads the unobserved sessions from the shared corpus, infers durable knowledge (project context stated in passing, user corrections, gotchas hit, non-obvious behaviour, patterns established), classifies each with a prefer-ungated tiebreaker, and enriches directly with no approval — project-wide context into insight/observations/, per-file facts into insight per-file entries — carrying claude-sessions provenance; only the minority that should bind future work becomes a rule-candidate or decision-candidate pulse proposal — then runs `cortex loop-session-observe --apply --proposals <file>` and summarises .cortex/pulse/reports/session-observe.md.
cortex-loop-test-runner
Tiered test-runner loop for a Cortex project — the only code-writing loop. Use for the scheduled test-runner task, or when the user says "run the test-runner loop", "run the test cascade", or "triage the failing tests". Runs `cortex loop-test-runner --collect`, classifies each pending failure in-session with the specflow-bugs discipline, runs `cortex loop-test-runner --fix-stage <results.json>`, and summarises .cortex/pulse/reports/test-failures.md.
cortex-pulse-distil
Weekly session-distillation loop for a Cortex project. Use for the scheduled weekly-curation bundle's distil member, or when the user says "run the distil loop", "what do I keep repeating", "mine the sessions for rule candidates", or "which workflows deserve a skill". Runs `cortex pulse-distil --collect`, performs the pattern judgment in-session — including the workflow-mining lens that proposes new skills — runs `cortex pulse-distil --propose`, and summarises .cortex/pulse/suggestions.md.
specflow-change-router
Classify every incoming user request against the project's spec tree (developer specs in `.specflow/specs/`, business specs in `.specflow/specs-business/`, and `_overview.md` folder docs) and route it to the correct action before any work begins. This skill is the mandatory entry point for ALL user interactions in a Specflow-managed project (any project with a `.specflow/specs/` directory, with or without a parallel `.specflow/specs-business/`). PROACTIVELY use this skill whenever the user says anything in a project under spec management — bug reports, feature requests, behavior changes, stakeholder questions, "what does this group do?", outcome/journey/metric talk, or anything that might touch a developer spec, a business spec, or a folder overview. Also triggers on "add a feature", "fix this bug", "change this behavior", "what does X do", "what's the goal of X", "why do we have X", and on requests that may have drifted between business and developer layers (e.g., a dev change that invalidates the business d
specflow-deep-onboard
Multi-pass codebase onboarding.
specflow-viewer
Generate the browsable spec site.
cortex-loop
Run a named Cortex maintenance loop.
cortex-loop-atlas-staleness
Monthly project-memory staleness review for a Cortex project. Use for the scheduled atlas-staleness task, or when the user says "run the atlas loop", "is the atlas stale", or "audit project memory". Invokes `cortex loop-atlas-staleness` and summarises .cortex/pulse/reports/atlas-review.md.
cortex-loop-onboarding-drift
Monthly scaffolding-drift review for a Cortex project. Use for the scheduled onboarding-drift task, or when the user says "run the onboarding-drift loop", "is the scaffolding current", or "check the CLAUDE.md block and indexes". Invokes `cortex loop-onboarding-drift` and summarises .cortex/pulse/reports/scaffolding-review.md.
cortex-loop-rule-decay
Weekly rule-obsolescence review for a Cortex project. Use for the scheduled rule-decay task, or when the user says "run the rule-decay loop", "which rules are stale", or "audit the compass rules". Invokes `cortex loop-rule-decay` and summarises .cortex/pulse/reports/rule-candidates.md.
cortex-loop-spec-drift
Daily spec-content drift detector for a Cortex project. Use for the scheduled spec-drift task, or when the user says "run the spec-drift loop", "have the specs drifted", or "which specs lag their code". Invokes `cortex loop-spec-drift` and summarises .cortex/pulse/reports/spec-drift.md.
cortex-pulse-hygiene
Daily deterministic hygiene sweep for a Cortex project. Use for the scheduled hygiene task, or when the user says "run the hygiene loop", "hygiene sweep", "project health check", or asks what unfinished or broken state the project has. Invokes `cortex pulse-hygiene` and summarises .cortex/pulse/reports/hygiene.md.
cortex-ingest
Retired — moved into cortex-archive-ingest. Use this when the user says "ingest this transcript", "ingest this RFP", "ingest this brief", "ingest this email", "ingest this design doc", "add this to project memory", "capture this call", "remember this decision", "log these stakeholders", or drops any raw document — trigger cortex-archive-ingest instead.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.