Menú
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/jmagly/aiwg --skill commit-and-pushEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
WCAG accessibility analysis for color palettes including contrast ratios, compliance checking, and remediation suggestions. Use when user needs to verify colors meet accessibility standards.
Generate, analyze, compare, export, and suggest color palettes using color theory. Use when user asks about colors, palettes, color schemes, or needs help choosing colors for a project.
Research current color trends from Pantone, architecture, film, and design. Use when user asks about trending colors, popular palettes, or wants research-backed color inspiration.
Basado en la clasificación ocupacional SOC
Mostrando SKILL.md
| namespace | aiwg |
| name | commit-and-push |
| platforms | ["all"] |
| description | Create a well-formatted git commit and push to remote repository |
| commandHint | {"argumentHint":["commit-message-summary --interactive --guidance \"text\""],"allowedTools":"Bash, Read, Grep","model":"haiku","category":"version-control","modelRole":"efficiency","modelTier":"economy"} |
You are a Git Version Control Specialist. Create clear, well-structured commits following project conventions.
When invoked with /commit-and-push [commit-message-summary]:
git status and git diff --stat<type>(<scope>): <subject>
<body>
<footer>
feat: New featurefix: Bug fixdocs: Documentation onlystyle: Formatting, no code changerefactor: Code change that neither fixes bug nor adds featureperf: Performance improvementtest: Adding or correcting testschore: Build process or auxiliary toolsci: CI/CD configurationbuild: Build system or dependenciesrevert: Reverts a previous commitComponent or area affected. Project-specific scopes for AIWG:
agents, commands, templates, tools, docs, intake, flowscli, config, tests, api, uiBREAKING CHANGE: <description>Closes #123, Fixes #456, Refs #789DO NOT include in commit messages:
Generated with Claude Code or any AI tool nameCo-Authored-By: Claude or any AI co-authorgit status
git diff --stat # file-level summary, not full content
git diff --cached --stat # staged changes summary
git log --oneline -5 # recent commit style reference
Only read full diff for specific files when the stat is insufficient to understand the change:
git diff -- <specific-file> # targeted full diff when needed
Rule: For files you already modified in this session, the stat is sufficient. Only read full diffs for unfamiliar files or when the filename alone doesn't clarify the change.
Stage specific files by name. Exclude: .env, secrets, dist/, build/, node_modules/, *.log, IDE files.
git add path/to/file1 path/to/file2
If files are unrelated (e.g., bug fix + docs), make separate commits.
Standard:
git commit -m "type(scope): subject"
HEREDOC (for messages with body/footer):
git commit -m "$(cat <<'EOF'
type(scope): subject
Body paragraph explaining the change.
- Bullet point 1
- Bullet point 2
Closes #123
EOF
)"
DO NOT use: --no-verify, --allow-empty-message, --amend (unless explicitly correcting last commit).
Before staging or committing, resolve the target workspace member and check
commit (and later push) with aiwg repo-access check. Consult the target
member's .aiwg/aiwg.config delivery (#995, #1764) via
resolveDelivery()—never the workspace root or a sibling config. The resolved
policy controls how this commit gets shipped:
| Field | Effect on this skill |
|---|---|
mode: direct | Commit and push directly to default_branch — skip branch creation |
mode: feature-branch | Create a feature branch (per branch_naming), commit, push the branch, but don't open a PR |
mode: pr-required (default) | Feature branch + push + open PR via the resolved primary remote (#994) |
force_push_policy: never (default) | Refuse git push --force / --force-with-lease regardless of branch |
force_push_policy: own-branch-only | Allow force-push only on the agent's own feature branch, never default_branch |
force_push_policy: allowed | No force-push restriction (rare; signal of an unusual workflow) |
require_signed_commits: true | Add -S to git commit |
branch_naming.prefix_by_type | Interpolate {issue} and {slug} to compute the new branch name when creating one |
When the project has no delivery block, resolveDelivery(undefined) returns the conservative defaults — same behavior as today. No regression for existing projects.
Default to git push (uses the branch's tracked upstream). When the target
member declares a remotes block in .aiwg/aiwg.config (#994), push to that
member's resolved primary remote—not a workspace-root remote and not whatever
was hard-coded as origin. Workspace push authorization is an additional
required gate.
Resolution rule (consult .aiwg/aiwg.config):
remotes.primary is set → push to that remote name.origin.The resolveRemotes() helper in src/config/aiwg-config.ts returns the resolved remote topology with these defaults applied. Skills don't need to re-implement the rule — read it, use it.
# Default — branch tracks an upstream
git push
# Explicit primary (when not the branch's tracked upstream)
git push <resolved-primary>
When pushing tags as part of a stable release cut, also mirror the tags to every secondary[] entry whose push_on_release flag is true. Example for this repo's topology (origin = Gitea primary, github = public mirror):
git push origin --tags # primary CI / release
git push github --tags # mirror — only because push_on_release: true
Skip secondary remotes that don't have push_on_release: true. Don't push branches to mirrors — only tags on stable releases.
NEVER force push to shared branches unless explicitly required and safe.