Skip to main content
Exécutez n'importe quel Skill dans Manus
en un clic
Dépôt GitHub

AI-running-coach

AI-running-coach contient 20 skills collectées depuis Andy-CH-BO-AN, avec une couverture métier par dépôt et des pages de détail sur le site.

skills collectés
20
Stars
2
mis à jour
2026-06-07
Forks
0
Couverture métier
4 catégories métier · 100% classifié
explorateur de dépôts

Skills dans ce dépôt

python-review-qa-loop
Analystes en assurance qualité des logiciels et testeurs

Use when working on Python code changes that should follow this repo's shared review and QA loop. Read the shared workflow docs, make the smallest viable patch, run relevant tests, capture results, and route DB, credentials, secrets, or Garmin password related changes through the shared security guidance.

2026-06-07
git-change-conventions
Développeurs de logiciels

Use when creating or naming branches, pull requests, or commits in this repository. Follow the repo's required type prefixes for branch and PR titles, and write detailed commit messages.

2026-06-07
git-change-conventions
Développeurs de logiciels

Antigravity adapter for the git-change-conventions skill. Read the canonical skill in ai/skills before acting.

2026-06-07
python-review-qa-loop
Analystes en assurance qualité des logiciels et testeurs

Antigravity adapter for the python-review-qa-loop skill. Read the canonical skill in ai/skills before acting.

2026-06-07
readme-pm-review
Développeurs de logiciels

Antigravity adapter for the readme-pm-review skill. Read the canonical skill in ai/skills before acting.

2026-06-07
token-decrease
Rédacteurs techniques

Default concise communication overlay for this repository. Read the canonical skill before acting, keep it active by default, and switch to normal wording when safety, irreversible actions, or clarity need more explicit phrasing.

2026-06-07
token-decrease
Développeurs de logiciels

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", "token decrease", or invokes /caveman. Also auto-triggers when token efficiency is requested.

2026-05-18
token-decrease
Développeurs de logiciels

Default concise communication overlay for this repository. Read the canonical skill before acting, keep it active by default, and switch to normal wording when safety, irreversible actions, or clarity need more explicit phrasing.

2026-05-18
token-decrease
Développeurs de logiciels

Default concise communication overlay for this repository. Read the canonical skill before acting, keep it active by default, and switch to normal wording when safety, irreversible actions, or clarity need more explicit phrasing.

2026-05-18
token-decrease
Développeurs de logiciels

Default concise communication overlay for this repository. Read the canonical skill before acting, keep it active by default, and switch to normal wording when safety, irreversible actions, or clarity need more explicit phrasing.

2026-05-18
git-change-conventions
Développeurs de logiciels

Use when creating or naming branches, pull requests, or commits in this repository. Follow the repo's required type prefixes for branch and PR titles, and write detailed commit messages.

2026-05-16
python-review-qa-loop
Analystes en assurance qualité des logiciels et testeurs

Use when working on Python code changes that should follow this repo's shared review and QA loop. Read the shared workflow docs, make the smallest viable patch, run relevant tests, capture results, and route DB, credentials, secrets, or Garmin password related changes through the shared security guidance.

2026-05-16
readme-pm-review
Spécialistes en gestion de projets

Use only when the user explicitly asks for a product-manager style review of a repository README. Read only the README first, do not infer undocumented features, and provide readability feedback, rewrite suggestions, and product-priority recommendations.

2026-05-16
git-change-conventions
Développeurs de logiciels

Use when creating or naming branches, pull requests, or commits in this repository. Follow the repo's required type prefixes for branch and PR titles, and write detailed commit messages.

2026-05-14
git-change-conventions
Développeurs de logiciels

Use when creating or naming branches, pull requests, or commits in this repository. Follow the repo's required type prefixes for branch and PR titles, and write detailed commit messages.

2026-05-14
python-review-qa-loop
Analystes en assurance qualité des logiciels et testeurs

Use when working on Python code changes that should follow this repo's shared review and QA loop. Read the shared workflow docs, make the smallest viable patch, run relevant tests, capture results, and route DB, credentials, secrets, or Garmin password related changes through the shared security guidance.

2026-05-13
python-review-qa-loop
Analystes en assurance qualité des logiciels et testeurs

Use when working on Python code changes that should follow this repo's shared review and QA loop. Read the shared workflow docs, make the smallest viable patch, run relevant tests, capture results, and route DB, credentials, secrets, or Garmin password related changes through the shared security guidance.

2026-05-13
readme-pm-review
Spécialistes en gestion de projets

Use only when the user explicitly asks for a product-manager style review of a repository README. Read only the README first, do not infer undocumented features, and provide readability feedback, rewrite suggestions, and product-priority recommendations.

2026-05-12
readme-pm-review
Spécialistes en gestion de projets

Use only when the user explicitly asks for a product-manager style review of a repository README. Read only the README first, do not infer undocumented features, and provide readability feedback, rewrite suggestions, and product-priority recommendations.

2026-05-12
readme-pm-review
Spécialistes en gestion de projets

Use only when the user explicitly asks for a product-manager style review of a repository README. Read only the README first, do not infer undocumented features, and provide readability feedback, rewrite suggestions, and product-priority recommendations.

2026-05-12