brycewang-stanford/commit
skills/41-sticerd-eee-sewage-econometrics-check/skills/commit/SKILL.md
Stage, commit, and push changes for the sewage project. Creates a branch, commits with a descriptive message, pushes, and optionally creates a PR. This skill should be used when asked to "commit", "save changes", "push", or "create a PR".
$ install --global
skillsauthnpx skillsauth add brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research commitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 20, 2026, 4:57 AM111.1s1 file scanned
SKILL.md
- name:
- commit
- description:
- Stage, commit, and push changes for the sewage project. Creates a branch, commits with a descriptive message, pushes, and optionally creates a PR. This skill should be used when asked to "commit", "save changes", "push", or "create a PR".
- argument-hint:
- [optional: commit message]
- allowed-tools:
- ["Bash", "Read", "Glob"]
Commit and Push
Stage changes, commit with a descriptive message, and push to remote.
Steps
- Check current state:
git status
git diff --stat
git log --oneline -5
- Create a branch from current state:
git checkout -b <short-descriptive-branch-name>
- Stage files — add specific files (never use
git add -A):
git add <file1> <file2> ...
Do NOT stage:
.claude/settings.local.json- Any files containing secrets or API keys
- Large data files (anything in
data/) - Temporary files (anything in
data/temp/)
- Commit with a descriptive message:
If $ARGUMENTS is provided, use it as the commit message. Otherwise, analyse the staged changes and write a message that explains why, not just what.
git commit -m "$(cat <<'EOF'
<commit message here>
Co-Authored-By: Claude Opus 4.6 <[email protected]>
EOF
)"
- Push and optionally create PR:
git push -u origin <branch-name>
gh pr create --title "<short title>" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points>
## Test plan
<checklist>
EOF
)"
- Merge and clean up (only if user confirms):
gh pr merge <pr-number> --merge --delete-branch
git checkout main
git pull
- Report the PR URL and what was merged.
Important
- Always create a NEW branch — never commit directly to main
- Exclude data files, temp files, and secrets from staging
- Use
--merge(not--squashor--rebase) unless asked otherwise - If the commit message from
$ARGUMENTSis provided, use it exactly - Follow existing commit message style (see recent
git log)
Related Skills
brycewang-stanford/thematic-analysis
development
VerifiedTrustedCommunity
Conduct rigorous thematic analysis (TA) of qualitative data following Braun and Clarke's (2006) six-phase framework. Use whenever the user mentions 'thematic analysis', 'TA', 'Braun and Clarke', 'qualitative coding', 'identifying themes', or asks for help analysing interviews, focus groups, open-ended survey responses, or transcripts to identify patterns. Also trigger for questions about inductive vs theoretical coding, semantic vs latent themes, essentialist vs constructionist epistemology, building a thematic map, or writing up a qualitative findings section. Covers all six phases, the four upfront analytic decisions, the 15-point quality checklist, and the five common pitfalls. Produces a Word document write-up and an annotated thematic map. Does NOT cover IPA, grounded theory, discourse analysis, conversation analysis, or narrative analysis — use a different method for those.
1,685SKILL.mdUpdated Jun 5, 2026
brycewang-stanford/slr-prisma
development
VerifiedTrustedCommunity
Guide users through writing a systematic literature review (SLR) following the PRISMA 2020 framework. Use this skill whenever the user mentions 'systematic review', 'systematic literature review', 'SLR', 'PRISMA', 'PRISMA 2020', 'PRISMA flow diagram', 'PRISMA checklist', or asks for help writing, structuring, or auditing a literature review that follows reporting guidelines. Also trigger when the user asks about inclusion/exclusion criteria for a review, search strategies for databases like Scopus/WoS/PubMed, study selection processes, risk of bias assessment, or narrative synthesis for a review paper. This skill covers the full PRISMA 2020 checklist (27 items), produces a Word document manuscript in strict journal article format, generates an annotated PRISMA flow diagram, and enforces APA 7th Edition referencing throughout. It does NOT cover meta-analysis or statistical pooling. By Chuah Kee Man.
1,685SKILL.mdUpdated Jun 5, 2026
brycewang-stanford/running-placebo-analysis
testing
VerifiedTrustedCommunity
Performs placebo-in-time sensitivity analysis with hierarchical null model and optional Bayesian assurance. Use when checking model robustness, verifying lack of pre-intervention effects, or estimating study power.
1,685SKILL.mdUpdated Jun 5, 2026
brycewang-stanford/running-causalpy-experiments
data-ai
VerifiedTrustedCommunity
Fit, summarize, plot, and interpret a chosen CausalPy experiment. Use after the causal method has been selected, including when configuring PyMC/sklearn models and scale-aware custom priors.
1,685SKILL.mdUpdated Jun 5, 2026