project-management
Ensures project integrity through automated database backups and semantic Git commit conventions.
Install
mkdir -p .claude/skills/project-management && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16845" && unzip -o skill.zip -d .claude/skills/project-management && rm skill.zipInstalls to .claude/skills/project-management
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Automated workflows for Git version control, database backups, semantic naming, and task tracking. Use this skill whenever the user asks to save progress, commit changes, or perform project management tasks.Key capabilities
- →Perform database backups using `mysqldump`
- →Apply semantic naming conventions for backups
- →Commit changes with semantic messages
- →Push committed changes to `origin main`
- →Maintain clear, descriptive naming for files, functions, and variables
- →Update task tracking documents like `tasks.md` and `implementation_plan.md`
How it works
This skill automates database backups with semantic naming, stages and commits changes using a specified format, and updates project task tracking documents.
Inputs & outputs
When to use project-management
- →Committing changes with semantic messages
- →Performing database backups
- →Saving project progress
- →Maintaining commit history standards
About this skill
Project Management Workflow
When working on this project, ALWAYS follow these rules and workflows to save time, maintain consistency, and prevent data loss:
1. Automated Backups
Before making significant changes or when requested to save/backup, perform a database backup.
- Use
mysqldumpto backup the Laragon MySQL database. - Semantic Naming: Always use
backup_iptv_nederland_YYYY_MM_DD_HH_mm.sqlfor precise versioning. - Remote Storage: After local backup, ensure the file is synced to a cloud provider or pushed to a secure remote storage to prevent loss if local files are deleted.
- Recovery: Refer to
.claude/recovery_plan.mdfor detailed restoration steps. - Command:
powershell -Command "& 'C:\laragon\bin\mysql\mysql-8.4.3-winx64\bin\mysqldump.exe' -u root iptv_nederland > backup_iptv_nederland_$((Get-Date).ToString('yyyy_MM_dd_HH_mm')).sql"
2. Git & Version Control
Always commit changes properly using semantic commit messages.
- Run
git add .to stage all changes. - Commit Format:
<type>(<scope>): <subject>feat: A new feature (e.g.,feat(frontend): setup Next.js homepage)fix: A bug fixdocs: Documentation only changes (tasks.md,implementation_plan.md)refactor: A code change that neither fixes a bug nor adds a featurechore: Routine tasks, dependency updates
- Push changes:
git push origin main
3. Semantic Naming Conventions
- Always use clear, descriptive names for files, functions, and variables.
- Maintain consistency with the existing codebase (e.g.,
PascalCasefor React components,camelCasefor functions, kebab-case for URLs).
4. Task Tracking
- Always keep
.claude/tasks.mdand.claude/implementation_plan.mdup to date. - After completing a task, update the checkmarks
[x]and increment the "Total" completed count intasks.md. - Never guess the project state; read
tasks.mdto see what is next.
When not to use it
- →When database backups are not required before significant changes
- →When semantic commit messages are not desired for version control
- →When task tracking documents are not in use
Limitations
- →Requires `mysqldump` for database backups
- →Enforces a specific semantic commit format
- →Relies on `.claude/tasks.md` and `.claude/implementation_plan.md` for task tracking
How it compares
This workflow enforces strict semantic naming for backups and commits, and mandates consistent updates to task tracking documents, unlike ad-hoc project management.
Compared to similar skills
project-management side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| project-management (this skill) | 0 | 3mo | No flags | Beginner |
| interactive-shell | 0 | 1mo | No flags | Intermediate |
| jira | 11 | 6mo | No flags | Beginner |
| add-vault-note | 1 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
interactive-shell
Jonghakseo
dev server, TUI, REPL, DB shell, 로그처럼 사용자 제어나 장시간 실행이 필요한 터미널 작업에 사용한다. AI 작업 위임에는 subagent를 사용한다.
jira
davila7
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.
add-vault-note
tradingstrategy-ai
Add a note to specific vault
agent-project-board-sync
ruvnet
Agent skill for project-board-sync - invoke with $agent-project-board-sync
taxonomy-management
DusanEngIt
Manage the skill taxonomy: add new skills, deprecate old ones, review and approve pending skill proposals from imports or employee free-text input, check for duplicates, and invalidate taxonomy cache. Use when HR needs to update taxonomy or clear a backlog of unreviewed skill proposals.
everjust-documents
ever-just
Operate the "Documents" app of an everjust.app Odoo 19 tenant (browse/create/move folders and files, upload, download, tag, migrate storage, point Documents at the tenant's private cloud) via the Odoo MCP/ORM. Use to read or mutate a tenant's documents — create a folder (dms.directory) or file (dms.