تشغيل أي مهارة في Manus بنقرة واحدة

ابدأ الآن

pr

النجوم٤٠

التفرعات٦

آخر تحديث٢٠ أبريل ٢٠٢٦ في ٠١:٠٤

Create a pull request with full validation. Use when ready to submit work for review.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

SteveGJones

SteveGJones/ai-first-sdlc-practices

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	pr
description	Create a pull request with full validation. Use when ready to submit work for review.
disable-model-invocation	true
argument-hint	[base-branch]

Create Pull Request

Run full validation, then create a PR if clean.

Steps

Run pre-push validation

/sdlc-core:validate --pre-push

If validation fails, report the issues and stop. Do NOT push or create PR.
Re-verify any test counts cited in the PR body.

--pre-push runs the pytest suite only. If the draft PR body cites results from integration smokes, E2E suites, soak tests, container tests, or any other harness outside local-validation.py, re-run those exact suites in this session and update the counts in the body to match the fresh run.

Example: a PR body saying "266 unit tests, 20/20 container smoke, 8/8 sequential E2E, 18/18 fresh-user-flow" requires pytest tests/ -q, bash tests/integration/workforce-smoke/run-containers.sh, bash tests/integration/workforce-smoke/run-e2e.sh, and bash tests/integration/workforce-smoke/run-fresh-user-flow.sh to all run this session before the PR is opened.

Session memory of test counts goes stale fast — fixtures grow, assertions drift, environments change. Only numbers you have just observed this session belong in the body. If a suite cannot run in this environment (missing binary, no Docker, etc.), delete the number from the body and say so explicitly rather than leaving a stale figure that cites another machine's result.

If the PR already exists and counts have drifted post-creation, update the body in place rather than closing and recreating:
```
gh pr edit <number> --body-file <updated-body.md>
```
Verify required artifacts exist:
- Feature proposal in docs/feature-proposals/
- Retrospective in retrospectives/
- If either is missing, warn the user and ask whether to proceed.
If validation passes, proceed:
- Check if the branch tracks a remote: git branch -vv
- Push to remote with tracking: git push -u origin <branch>
- Base branch defaults to main unless $ARGUMENTS specifies otherwise
Create the PR using gh pr create:

gh pr create --title "<short title under 70 chars>" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points summarizing the changes>

## Changes
<List of files modified/created>

## Test plan
- [ ] `/sdlc-core:validate --pre-push` passes
- [ ] CI pipeline passes
<additional test steps as needed>

🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"

Report the PR URL to the user.

المزيد من هذا المستودع

نفس المستودع

kb-ingest-bulk

SteveGJones/ai-first-sdlc-practices

Parallel map-reduce bulk ingest for large source sets. Map phase dispatches read-only knowledge-extractor agents (≤N-wide, default Haiku) emitting per-source JSON extracts; Python routes extracts by target library file (fuzzy-merging new topics, pre-allocating new files, flagging oversized topics); reduce phase dispatches one agent-knowledge-updater per file (parallel, one writer per file); single shelf-index rebuild + one log.md entry. Resumable. Supersedes kb-ingest-batch.

2026-06-0540

kb-init

SteveGJones/ai-first-sdlc-practices

Initialise a project for knowledge base use. Appends the [Knowledge Base] section to the project's CLAUDE.md, creates the library/ directory structure, optionally seeds with three example library files from the Agentic SDLC research, and reports next steps. Run once after installing sdlc-knowledge-base.

2026-06-0540

kb-ingest-batch

SteveGJones/ai-first-sdlc-practices

Drive agent-knowledge-updater over a batch of staged files in library/raw/. Tracks progress in .batch-progress.json for resume support. Sequential by default; --parallel <N> opt-in (max 5). Single shelf-index rebuild and one consolidated log.md entry at the end.

2026-06-0540

kb-lint

SteveGJones/ai-first-sdlc-practices

Health-check the project knowledge base. Looks for contradictions between files, stale claims that newer sources have superseded, orphan files with no inbound cross-references, important concepts mentioned but lacking their own page, missing cross-references, and data gaps. Returns a structured report; does not auto-fix.

2026-05-0640

kb-prepare-batch

SteveGJones/ai-first-sdlc-practices

Stage source files into library/raw/, converting non-markdown formats via markitdown (PDF/DOCX/PPTX/XLSX/HTML/CSV) or pandoc (TeX/EPUB/RST/ORG). Adds provenance frontmatter. No agent dispatch.

2026-05-0540

kb-stats

SteveGJones/ai-first-sdlc-practices

Pure-Python knowledge base statistics dashboard. Reads shelf-index and log.md; emits Inventory, Layer distribution, Domain distribution, Recent Activity, and Staleness sections. No agent dispatch. Read-only.

2026-05-0340

Create Pull Request

Run full validation, then create a PR if clean.

Steps

Run pre-push validation

/sdlc-core:validate --pre-push

If validation fails, report the issues and stop. Do NOT push or create PR.

Re-verify any test counts cited in the PR body.

--pre-push runs the pytest suite only. If the draft PR body cites results from integration smokes, E2E suites, soak tests, container tests, or any other harness outside local-validation.py, re-run those exact suites in this session and update the counts in the body to match the fresh run.

Example: a PR body saying "266 unit tests, 20/20 container smoke, 8/8 sequential E2E, 18/18 fresh-user-flow" requires pytest tests/ -q, bash tests/integration/workforce-smoke/run-containers.sh, bash tests/integration/workforce-smoke/run-e2e.sh, and bash tests/integration/workforce-smoke/run-fresh-user-flow.sh to all run this session before the PR is opened.

Session memory of test counts goes stale fast — fixtures grow, assertions drift, environments change. Only numbers you have just observed this session belong in the body. If a suite cannot run in this environment (missing binary, no Docker, etc.), delete the number from the body and say so explicitly rather than leaving a stale figure that cites another machine's result.

If the PR already exists and counts have drifted post-creation, update the body in place rather than closing and recreating:

gh pr edit <number> --body-file <updated-body.md>

Verify required artifacts exist:

Feature proposal in docs/feature-proposals/
Retrospective in retrospectives/
If either is missing, warn the user and ask whether to proceed.

If validation passes, proceed:

Check if the branch tracks a remote: git branch -vv
Push to remote with tracking: git push -u origin <branch>
Base branch defaults to main unless $ARGUMENTS specifies otherwise

Create the PR using gh pr create:

gh pr create --title "<short title under 70 chars>" --body "$(cat <<'EOF' ## Summary <1-3 bullet points summarizing the changes> ## Changes <List of files modified/created> ## Test plan - [ ] `/sdlc-core:validate --pre-push` passes - [ ] CI pipeline passes <additional test steps as needed> 🤖 Generated with [Claude Code](https://claude.com/claude-code) EOF )"

Report the PR URL to the user.