knowledge-management
Create or update knowledge files for a feature area. Use when the user says "update knowledge", "create knowledge file for X", "document this feature", or after completing a feature that needs knowledge documentation.
- License 许可
- MIT
- 最近更新
- 2026-10-24
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- knowledge-management
- description
- Create or update knowledge files for a feature area. Use when the user says "update knowledge", "create knowledge file for X", "document this feature", or after completing a feature that needs knowledge documentation.
03 SKILL.md 正文
Knowledge Management
This skill guides you through creating or updating files in the knowledge/ directory. Follow the conventions defined in .cursor/rules/knowledge.mdc.
Step 1: Determine the Action
Use AskQuestion:
prompt: "What would you like to do?"
options:
- Create a new knowledge file for a feature area
- Update an existing knowledge file
- Review all knowledge files for staleness
Creating a New Knowledge File
Step 2a: Identify the Feature Area
Ask the user which feature area to document, or infer it from the conversation context. The file should be named after the feature area in lowercase with underscores (e.g., knowledge/billing.md, knowledge/auth.md).
Step 3a: Explore the Codebase
Read the source code for the feature area thoroughly:
- Identify the key modules, classes, and functions
- Trace the main code paths and data flow
- Note design decisions that are not obvious from the code alone
- Look for edge cases, gotchas, and non-obvious behaviors
Also read knowledge/architecture.md to understand how this area fits into the overall system.
Step 4a: Draft the Knowledge File
Write the file following this structure:
# <Feature Area Name>
<One or two sentences describing what this area does.>
## Design Decisions
<Why it works the way it does. Trade-offs, constraints, alternatives considered. Use a heading per decision if there are several.>
## API Surface
<Key classes, functions, types, and their relationships. Focus on what another developer (or the AI) needs to know to work in this area correctly.>
## Key Learnings / Gotchas
<Non-obvious behaviors, edge cases, things that broke before, common mistakes to avoid.>
Step 5a: Write and Confirm
Write the file to knowledge/<feature-area>.md. Tell the user what was created and suggest they review it.
Updating an Existing Knowledge File
Step 2b: Identify What Changed
Determine which knowledge file needs updating. This can come from:
- The user specifying a file directly
- A feature that was just implemented or modified
- A bug fix that revealed a non-obvious behavior
Step 3b: Read Current State
Read the existing knowledge file and the relevant source code. Identify which sections are stale or incomplete.
Step 4b: Rewrite Affected Sections
Update only the sections that need changes. Knowledge files describe the present state — rewrite sections entirely rather than appending notes or changelogs. Keep the same structure (Design Decisions, API Surface, Key Learnings / Gotchas).
Step 5b: Write and Confirm
Write the updated file. Tell the user what was changed and why.
Reviewing All Knowledge Files
Step 2c: Scan for Staleness
For each file in knowledge/:
- Read the knowledge file
- Check if the source code it describes has changed significantly since the file was last written
- Flag files that appear outdated
Step 3c: Report
Present a summary listing each knowledge file with its status:
- Current — the file accurately reflects the source code
- Needs update — the source code has diverged; explain what looks stale
- Missing — a significant feature area has source code but no knowledge file
Use AskQuestion with allow_multiple: true to let the user pick which files to update, then follow the update flow above for each.
04 同仓库更多 Skills
write-pytest
Write pytest tests for any Python codebase. Use when the user asks to write tests, create tests, add tests, or test a module/service/endpoint/function. Framework-agnostic; routes to framework-specific helpers when signals are detected. Follows a research-then-discuss-then-write flow.
quality-assurance
Run quality assurance checks on the current chat session — pre-task validation, post-task checklist, and code review. Use when finishing a task, before committing, or when the user asks for a QA review.
python-developer
Python developer umbrella — installs Python coding conventions and bundles companion skills (best practices, testing, dependency management) in a single setup. Use when the user asks to set up Python development conventions, install Python skills, or says "set up Python development".
python-best-practices
Comprehensive Python coding conventions and best practices. Use when the user asks about Python conventions, coding patterns, best practices, code style, anti-patterns, or "how should I write this" in Python.
pyramid-library
Library Developer persona: developing standalone Pyramid extensions (own repo, own package) that expose includeme for external consumers. Use when the user builds a reusable Pyramid library, designs includeme for consumers, registers custom directives/tweens/request methods, or tests a library with a proper app.
pyramid-developer
Pyramid framework conventions — configuration/registry, module system with includeme, pyramid_services, models, Cornice REST, ACL authorization, and transactions. Use when setting up Pyramid development conventions for a project.